From dfac9b1404d78d1abb793431bb034a2cc78ce270 Mon Sep 17 00:00:00 2001 From: Piotr Sarnacki Date: Sun, 19 Sep 2010 18:47:41 +0200 Subject: Strengthen documantation on engine's migrations and seed data MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: José Valim --- railties/lib/rails/engine.rb | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'railties/lib/rails/engine.rb') diff --git a/railties/lib/rails/engine.rb b/railties/lib/rails/engine.rb index 8387f277c9..fd91185a47 100644 --- a/railties/lib/rails/engine.rb +++ b/railties/lib/rails/engine.rb @@ -257,6 +257,21 @@ module Rails # # This code will use my_engine.user_path(@user) to generate proper route. # + # == Migrations & seed data + # + # Engines can have their own migrations. Default path for migrations is exactly the same + # as in application: db/migrate + # + # To use engine's migrations in application you can use rake task, which copies them to + # application's dir: + # + # rake railties:copy_migrations + # + # If your engine has migrations, you may also want to prepare data for the database in + # seeds.rb file. You can load that data using load_seed method, e.g. + # + # MyEngine::Engine.load_seed + # class Engine < Railtie autoload :Configurable, "rails/engine/configurable" autoload :Configuration, "rails/engine/configuration" -- cgit v1.2.3