Closed cnorm35 closed 1 year ago
Re-orders post-install instructions to create DB prior to running the noticed generator.
Running the instructions as-is raises a PG::ConnectionBad database "jumpstart_development" does not exist error .
PG::ConnectionBad
I agree with the changes in #191 to only have to migrate once, but running the noticed generator returns
1. Run "rails db:migrate"
as one of the Next Steps along with the option to run the pending migrations in the browser so this seems like a clearer approach.
I was trying to avoid running the migrate twice, so if you move the noticed model after, I think you'll have to do it again. Maybe we need to fix noticed or something?
Re-orders post-install instructions to create DB prior to running the noticed generator.
Running the instructions as-is raises a
PG::ConnectionBad
database "jumpstart_development" does not exist error .I agree with the changes in #191 to only have to migrate once, but running the noticed generator returns
1. Run "rails db:migrate"
as one of the Next Steps along with the option to run the pending migrations in the browser so this seems like a clearer approach.