rails-engines

I am following the guide http://edgeguides.rubyonrails.org/plugins.html and it seems to be slightly outdated. Could you have a look on it and tell me which sections should be done in a different way in Rails 3? EDIT1: Links to alternative tutorials are also very welcome! You're right, that guide isn't the best (the last changelog entry is April 2010). Instead, I'd recommend you read: https://github.com/radar/guides/blob/master/gem-development.md I bumped into this question, and the answers are now outdated. The railsguide is currently up to date: http://guides.rubyonrails.org/engines.html The

I have rspec suite for parent app, and also some spec for engines attached. What I want is to run them with one command. Is there a way to include my gems paths into rspec load path? Or should I write rake task for this? I think this is an interesting question, but my opinion is that Rails Engines should be treated as an independent code base and therefore not tested in your parent app. The effect is that you'd treat a Rails Engine in your parent app much like you treat other gems (EG, devise, which is actually a Rails Engine). But let's say you have parent app functionality that relies on a

I am working on a rails engine and I have a problem with the helpers. Apparently this is a known "problem" but there's not a lot of solutions out there. The problem is that I have an AuthenticationHelper which I want to access globally - but it's not working. I've read that you could add a few lines to your init.rb but it does not seem to have any effect. Any idea what the best way to make an application available in an engine? EDIT: Fixed it- Just put the code (from the link) in the engine.rb instead. Put this code in engine.rb: config.to_prepare do ApplicationController.helper(MyEngineHelper

I'm having some problem accessing Rails.root from my rails engine, that I'm creating. I need to fetch a yml config file from the main app. Is there any "best practices" for handling configurations for your engines? Let's assume you have a module attribute for that. # lib/my_engine.rb module MyEngine mattr_accessor :app_root end Then you can load it from the initialize block like so: # lib/my_engine/engine.rb module MyEngine class Engine < Rails::Engine initializer "my_engine.load_app_root" do |app| MyEngine.app_root = app.root end end end Instead use Rails.root use: MyEngine::Engine.root ;D 来源

I'm creating a rails mountable engine plugin which uses the gem "jquery-rails". I added this code in .gemspec file s.add_dependency "jquery-rails", "~> 3.0.1" and run bundle install , bundle update . (BTW is this adding necessary? Since rails mountable engine already added "rails 4.0.1" which in turn required "jquery-rails 3.0.4" as its dependency from the start?). In app/assets/javascript/mountable_engine_name/application.js //= require jquery //= require jquery-ujs //= require_tree . But when I run the server on test/dummy/ and access any template which uses the tag <%= javascript_include

This is more for experimentation - I am aware that I can do this with --full but I wanted the functionality of namespacing in the app to avoid conflicts The idea is to have a main app - which handles authentication, common items, admin screens etc Then creating engines to add further functionality like crm cms blog wiki forum etc These engines I can pick and choose as I need for whatever kind of app I am building. Is this possible? Is it just the case of applying both --mountable and --full options? Experimenting - would there be any issue if I use the full option add rspec and then simple add