Hi Dmytrii, RefineryCMS *always* runs as an engine, so using it in an existing app is much the same as using it in a new app. The only place where it might fight with your other stuff is authentication. Refinery expects to use Devise. If you're already using that, you're fine. If not using devise, and you want to do shared login with refinery, then I think you'll need to patch stuff.
Craig On 5/09/2011, at 8:09 PM, Dmytrii Nagirniak wrote: > You can go to http://refinerycms.com for overview information and you > can to go https://github.com/resolve/refinerycms/ to see the > repository. > > Thanks. But I can't find the pointers about using it as part of an existing > app (as an Engine). > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
