Skip to content

Commit

Permalink
changing over to db:setup which closes #191
Browse files Browse the repository at this point in the history
  • Loading branch information
btbonval committed Feb 7, 2015
1 parent 5eb40ff commit bc4bb1d
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,13 @@ Installation steps:
* in the console, `git clone https://github.com/publiclab/plot2.git` or `git clone git@github.com:publiclab/plots2.git`
* `cd` into the new 'plots2' directory
* `bundle install`
* create a database (usually in mysql) and grant permissions to youruser
* copy config/database.yml.example to config/database.yml and add database login info for development and/or production (a separate database for testing is helpful too)
* `rake db:migrate` to set up the database
* grant database creation permissions to your user
* copy `config/database.yml.example` to `config/database.yml` and add database login info for development and/or production (a separate database for testing is helpful too)
* `rake db:setup` to set up the database
* if there are any errors, try one of these two fixes:
* run `rake db:migrate`
* OR
* in MySQL, `drop database XXX;` for each database in `config/database.yml` and then try `rake db:setup` again
* `rake db:seed` to populate it with initial data
* `passenger start` to start up the app
* in a browser, navigate to http://localhost:3000
Expand Down

1 comment on commit bc4bb1d

@jywarren
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @btbonval - was there a reason you kept rake db:migrate as a fallback? Now that I'm trying to deprecate spatial_adapter and get sqlite-compatible (for new developers), I'm more interested in just never running migrate, because there are ENGINE directives and spatial things I'd like to never have to deal with, but don't want to rewrite the schema/migration history. For example, I'd prefer to add a new migration than to change early migrations in #429 and #433.

I did see an error with rake:db setup recently, but migrate didn't solve the issue.

Please sign in to comment.