diff options
| author | Les Nightingill <codehacker@comcast.net> | 2013-03-31 18:21:41 -0700 |
|---|---|---|
| committer | Les Nightingill <codehacker@comcast.net> | 2013-03-31 18:21:41 -0700 |
| commit | 62b9723fbf166f441316e6ed53bb96b8e2995027 (patch) | |
| tree | 9ff477696cf53fd78ccb22650fcad13b3a7e5a69 | |
| parent | da9031ae26d5b377a465aae925f1c3cc9d2c2453 (diff) | |
| download | rails-62b9723fbf166f441316e6ed53bb96b8e2995027.tar.gz rails-62b9723fbf166f441316e6ed53bb96b8e2995027.tar.bz2 rails-62b9723fbf166f441316e6ed53bb96b8e2995027.zip | |
as of Rails 3.2.13 it appears that importing an engine's migration into the host app is achieved by rake blorgh_engine:install:migrations
| -rw-r--r-- | guides/source/engines.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/engines.md b/guides/source/engines.md index ac76f00832..22c090e04b 100644 --- a/guides/source/engines.md +++ b/guides/source/engines.md @@ -461,7 +461,7 @@ NOTE: Other engines, such as Devise, handle this a little differently by making The engine contains migrations for the `blorgh_posts` and `blorgh_comments` table which need to be created in the application's database so that the engine's models can query them correctly. To copy these migrations into the application use this command: ```bash -$ rake blorgh:install:migrations +$ rake blorgh_engine:install:migrations ``` If you have multiple engines that need migrations copied over, use `railties:install:migrations` instead: |