search for: engine_nam

I created a new Rails 3.2.6 engine via a command like this: $ rails plugin new $engine_name --skip-bundle -d $database_type -T --dummy-path=spec/dummy --full --mountable Then, I set it up with RSpec 2.11.0, and included the "pry-rails" gem as a dependency: $ grep pry-rails $engine_name.gemspec s.add_development_dependency ''pry-rails'', ''~> 0.1....

It appears that you cannot use migrations (out of the box) with mysql 4.0.16, because when creating a table, the statement says "ENGINE=InnoDb", instead of "TYPE=InnoDB". Looking at the source code for the adapter, this appears to be hard coded. Is there any supported way to make this work with older versions of MySQL? David

...h either. Since it never reached consensus I figured I''d try another approach that''s worked well for Pivotal Labs'' Desert system (we''ve been doing things that way for several years). The basic idea is to add a method to the Migration class: migrate_engine(engine_name, target_version). You have to manually add a migration to the app''s migrations, but that''s nice and explicit the way we want it to be. The migration looks something like this: class UpgradeToMarchRelease < ActiveRecord::Migration def self.up migrate...

...d generator, which installs the engines plugin automatically if it doesn''t already exist (Ticket #122) - Added a default VERSION module to generated engines (Ticket #123) - Refactored copying of engine''s public files to a method of an Engine instance. You can now call Engines.get(:engine_name).copy_public_files (Ticket #108) - Changed engine generator templates from .rb files to .erb files (Ticket #106) - Fixed the test_helper.erb file to use the correct testing extensions and not load any schema - the schema will be cloned automatically via rake test:engines - Fixed problem when runni...