Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-12-22 10:10:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Revert "Use db:schema:load instead of db:migrate"

Browse source 
This reverts commit 3c5f28869b,
which did not function properly on the continuous integration server.
This commit is contained in:
Dan Rice 2013-03-05 01:00:24 -05:00
parent 3c5f28869b
commit 34e0c2b13a
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/installation.textile
View file

@ -104,9 +104,9 @@ h3. Populate your database with the Tracks schema
Open a terminal and change into the root of your Tracks directory. Enter the following command:
bc. bundle exec rake db:schema:load RAILS_ENV=production
bc. bundle exec rake db:migrate RAILS_ENV=production
This will populate your database with the required schema for Tracks. If you are using SQLite3, it is not strictly necessary, because the SQLite3 database included with Tracks already has the schema included in it, but it should not do any harm to run the command (nothing will happen if it is up to date).
This will update your database with the required schema for Tracks. If you are using SQLite3, it is not strictly necessary, because the SQLite3 database included with Tracks already has the schema included in it, but it should not do any harm to run the command (nothing will happen if it is up to date).
h3. Precompile assets

2
lib/tasks/continuous_integration.rake
View file

@ -1 +1 @@
task :ci => ['db:schema:load', :test, :cucumber]
task :ci => ['db:migrate', :test, :cucumber]