Mountable engines was totally new to me before I watched this screencast. Therefor I have a couple of questions..
Would a use case example be to create a authentication and profile engine, then a blog engine, a forum engine etc and combine them all together under a "umbrella" app?
Is the mentioned use case a good way to create better scalable apps?
I guess you can create a engine within a engine as well?
I get the following error after I've set up the rails pre RVM, installed rails --pre and then try to run rails / rails -v:
ruby
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:925:in`report_activate_error': Could not find RubyGem rails (>= 0) (Gem::LoadError)
from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:243:in `activate_dep'
from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:235:in `activate'
from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:1306:in`gem'
from /usr/local/bin/rails:18:in `<main>'
If I do ruby -v it outputs ruby 1.9.2p180, but there looks like there is a linking error or something, any ideas?
+1
Mountable engines was totally new to me before I watched this screencast. Therefor I have a couple of questions..
Would a use case example be to create a authentication and profile engine, then a blog engine, a forum engine etc and combine them all together under a "umbrella" app?
Is the mentioned use case a good way to create better scalable apps?
I guess you can create a engine within a engine as well?
I get the following error after I've set up the rails pre RVM, installed rails --pre and then try to run rails / rails -v:
If I do ruby -v it outputs ruby 1.9.2p180, but there looks like there is a linking error or something, any ideas?