forked from saasbook/MultiMeet
-
Notifications
You must be signed in to change notification settings - Fork 1
Heroku Deployment
Kevin Chien edited this page May 13, 2019
·
3 revisions
- run:
heroku git:clone -a multi-meet
- this clones into a new directory (separate from your existing MultiMeet directory)
- so use this new directory for pushing to heroku
- if don’t have ref to origin: run
git remote add origin https://github.com/Aakup/MultiMeet
- run
git pull origin master
, thengit push heroku master
- remember to run
heroku rake db:migrate
- safest option: reset database
heroku pg:reset DATABASE
(drops database), then runheroku rake db:reset
-
git push heroku master
-> unpushed refs solution: - do:
git pull heroku master
, resolve merge conflict - OR force push
- column missing solution:
-
heroku pg:reset DATABASE
(does db:drop for you) heroku db:migrate
- undefined method of model even if migration ran solution:
heroku restart
- link on on stack overflow