aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/migrations.md
diff options
context:
space:
mode:
authorJay Hayes <jay@bignerdranch.com>2013-08-29 11:18:07 -0500
committerJay Hayes <jay@bignerdranch.com>2013-08-29 11:18:07 -0500
commit5f08154230f69a8aee88d72e09fe088bf728f506 (patch)
tree9df38b2eee7fa4f22967705b3e03ade5268697c0 /guides/source/migrations.md
parentd4863f30de023d0f6817afcddc114889493e6d3c (diff)
downloadrails-5f08154230f69a8aee88d72e09fe088bf728f506.tar.gz
rails-5f08154230f69a8aee88d72e09fe088bf728f506.tar.bz2
rails-5f08154230f69a8aee88d72e09fe088bf728f506.zip
Add documentation for rake db:setup task
Diffstat (limited to 'guides/source/migrations.md')
-rw-r--r--guides/source/migrations.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md
index 55bb89bd71..d154dae752 100644
--- a/guides/source/migrations.md
+++ b/guides/source/migrations.md
@@ -692,6 +692,11 @@ Neither of these Rake tasks do anything you could not do with `db:migrate`. They
are simply more convenient, since you do not need to explicitly specify the
version to migrate to.
+### Setup the Database
+
+The `rake db:setup` task will create the database, load the schema and initialize
+it with seed data.
+
### Resetting the Database
The `rake db:reset` task will drop the database and set it up again. This is