Re: Rails CMS best fit

GBH
Sat, 20 Oct 2012 18:02:32 -0000

Hey Erwin

- ComfortableMexicanSofa is mounted as a catch-all on the root path as a
default. I''ll make it mountable soon, but it works just the same right
now.
- There''s concept of ''sites'' so you can serve
completely different content
based on the subdomain. But technically it can take care of everything that
doesn''t hit your application routes.
- Comes with simple httpauth that you can replace with Devise or whatever
else you want. See wiki for example.
- Doesn''t have user permissions though (it has no concept of users).
This
is something that is possible to hack in as part of the authorization.

Let me know if you have any questions. I might be able to help.

Oleg

On Thursday, October 18, 2012 5:31:17 AM UTC-4, Erwin
wrote:
>
> Thanks for your feedback..
>
> I also looked into Locomotive, good ( I know  Mongoid) but the project
> needs MySQL...
> After looking at other existing Rails CMS : Alchemy, Radiant,
> Refinery, Comfortable Mexican Sofa ( C.M.S. !) and also browserCMS, my
> feeling is that none of them are actually true good engines for our
> project ..  rather than describing what I mean by that , better giving
> an example of a good one : "forem" (
https://github.com/radar/forem )
>
> ''forem'' brings a complete forum app as an engine to our
existing rails
> web apps:
> - can be mounted at root or subdomain level,
> - reuse our Devise authentication module, forem initialize with the
> declared ''user'' class, and
''current_user'' helper
> - forem internal authorization is based on CanCan, and  permissions
> can be superseded within the declared ''user'' class
>
> said that, we are currently looking into Alchemy code ( good
''content''
> management ) to see how we could adapt it (to the ''forem''
way)
> regarding authentication and authorization ( I know that the new
> Refinery aims at using authentication/authorization engines.... but
> Refinery cannot be mounted at subdomain level which is mandatory in
> our project
>
> thanks again
>
>
>
> On 17 oct, 16:12, masta Blasta
<li...-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:
> > Kad Kerforn wrote in post #1080098:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > I already have a project with multiple subdomains under
development
> > > ( Rails 3.2.8 , MySQL,  Haml , Devise , Cancan )
> >
> > >www.myproject.com is the main site
> > > many subdomains will be created   :  sub1.myproject.com,
> > > sub2.myproject.com,  sub3.myproject.com, ...
> >
> > > We need now to add CMS functionalities to the main domain and to
each
> > > subdomain, ( different layouts , different sets of pages )
> >
> > > What could be currently  the best CMS engine choice ? ( at least
the
> > > most adapted to this goal..)
> > > Radiant , Alchemy Refinery or even Locomotive ( with this one, I
know
> > > we should switch to Mongoid ORM, but why not ..) or any other
> > > one ...
> >
> > > thanks for feedback
> >
> > I''ve just started building a site with BrowserCMS.
It''s fairly well
> > featured, and allows for easy integration of outside controllers and
> > models. Documentation is good - not great - however the developers are
> > really responsive in the google group.
> > here is the project:https://github.com/browsermedia/browsercms
> > One thing about browserCMS is that it uses it''s own
authentication
> > methods so you might have issues using Devise.
> >
> > I also tried locomotive but i found it lacking in features and
> > documentation. Also the switch to mongoid has a learning curve to it
if
> > you''re not already familiar. Locomotive has potential, but it
is still
> > early in development.https://github.com/locomotivecms
> >
> > --
> > Posted viahttp://www.ruby-forum.com/.
>

--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit