rails-engines

A lot has been written about engine development, and using a dummy app for testing. In our case we're developing an engine that is not a stand-alone entity, but has dependencies on a real Rails 3 application. We still want this code to live in an engine, and not become part of the app, because the engine's job is to import data from a legacy system that has its own tables and model mappings, and we want to eventually remove it again. The data mappings between the old legacy tables and the new schema are complex, and we want to TDD (using rspec) the engine. I've followed Jose Valim's book

As it stands now, you can't reopen Engine classes contained within the engine's /app directory by simply adding the same class in the parent app's /app dir. For example: /my_engine/app/controllers/users_controller.rb /my_app/app/controllers/users_controller.rb The file from my_engine will not even load if there is a file with the same name in the parent app. More details here: http://www.cowboycoded.com/2011/02/28/why-you-cant-reopen-rails-3-engine-classes-from-the-parent-app/ I am looking for a workaround that will allow me to drop the same filename/class in the same path as the parent app,

I'm currently experimenting with moving functionality into engines. It works nicely so far, but I'm a bit confused why certain parts of the engine are always automatically reloaded when something changed, and some are not. Specifically, when adding a helper method, I have to restart the Rails server, otherwise it is not seen by Rails. Is this normal behavior? Here's the relevant part of my engine: components/iq_list.rb # encoding: utf-8 require 'iq_list/engine' # Load IqList Modules module IqList extend ActiveSupport::Autoload autoload :Helpers autoload :Models autoload :Controllers end

So I keep getting the error: No route matches {:action=>"create", :controller=>"xaaron/api_keys"} Which is thrown in the test: it "should not create an api key for those not logged in" do post :create expect(response).to redirect_to xaaron.login_path end when I go to spec/dummy and run the rake routes command I see: api_keys GET /api_keys(.:format) xaaron/api_keys#index POST /api_keys(.:format) xaaron/api_keys#create new_api_key GET /api_keys/new(.:format) xaaron/api_keys#new edit_api_key GET /api_keys/:id/edit(.:format) xaaron/api_keys#edit api_key GET /api_keys/:id(.:format) xaaron/api_keys

I've built myself a Rails Engine that requires that the main app have a Users table. I need to be able to create a relationship between one of the models in my engine and the Users table in the main app. Is this more complicated than just saying belongs_to :user ? I'm getting an error that says the User object is nil, but when I use the console it returns the right user. My assumption is that Rails assumed my belongs_to :user call meant a User's class in the same namespace as the engine, i.e. MyEngine::User. Is there a way for me to explicitly specify that the User class is in the main app's

I have a Rails Engine, where I want to use Devise. I installed devise like normal following this guide . I added this in my engine devise.rb: Devise.setup do |config| config.router_name = :cms_user end I added this in my routes file: Cms::User::Engine.routes.draw do devise_for :users, { class_name: 'Cms::User', module: :devise } end I added this in my routes: devise_for :users, { class_name: 'Cms::User', module: :devise } However I keep getting this error: undefined method 'cms_user' What am I doing wrong ? Here's the how to: Rails plugin new cms --mountable -d postgresql 2: Install devise

In one hand, I have a mountable engine let's say Front Front contain my assets and couple of pages It's isolated from MainApp. I don't want it to touch the main app. In the other hand I want my MainApp using layout and partial of the Front. So I setup the layout this way : class ApplicationController < ActionController::Base layout 'front/application' end But the front/application refer to engine partial directly, because of isolation, like this render 'header' # front/ prefix is not required So the MainApp views try to load app/views/application/header instead of app/views/front/application

I have a Rails app that I am trying to integrate a Rails engine in to. The host app has some catch all routes: # magic urls match '/' => 'admin/rendering#show' match '*path/edit' => 'admin/rendering#show', :defaults => { :editing => true } match '*path' => 'admin/rendering#show' It looks like the engine routes are loaded after the application catches all routes. /sitemap.xml(.:format) {:format=>"xml", :controller=>"admin/sitemaps", :action=>"show"} /(.:format) {:controller=>"admin/rendering", :action=>"show"} /*path/edit(.:format) {:controller=>"admin/rendering", :action=>"show"} /*path {