git status
git add .
git commit
git push Stage_xx
git checkout main
git branch -D Stage_xx
git pull
- Create (new name: recipes-2021)
heroku create recipes-2021
- Set master key on Heroku
heroku config:set RAILS_MASTER_KEY=`cat config/master.key`
or
heroku config:set RAILS_MASTER_KEY=`cat config/credentials/production.key`
if prod.env
heroku config:set RAILS_MASTER_KEY=`cat config/credentials/production.key`
heroku config:set RAILS_MASTER_KEY=content of production
else
heroku config:set RAILS_MASTER_KEY=`cat config/master.key`
heroku config:set RAILS_MASTER_KEY=content of master.key
- Create ProcFile (touch Procfile)
web: bundle exec rails s
release: rails db:migrate
- Add or check Linux platform to Gemfile.lock
bundle lock --add-platform x86_64-linux
PLATFORMS
x86_64-darwin-20
x86_64-linux
- Git repo update:
git status
git add .
git commit
git push Stage_xx
git checkout main
git branch -D Stage_xx
git pull
- Push resource
git push heroku main
or
git push heroku Stage_xx:master
- On Heroku in console
heroku run rake db:migrate
heroku run rake db:seed
heroku run console
heroku logs --tail
heroku config -a recipes-2021
heroku config:set S3_BUCKET_NAME=reciperail
heroku run rails console
Rails.application.credentials.config
Run
heroku open
Setting Change Boot Timeout (https://tools.heroku.support/limits/boot_timeout) The new boot timeout will take effect after your next deployment. You can redeploy your code without any changes by running:
heroku login
heroku create
echo "web: bundle exec puma -C config/puma.rb" >> Procfile
bundle lock --add-platform x86_64-linux
heroku addons:create heroku-postgresql:hobby-dev
heroku buildpacks:add heroku/ruby
heroku buildpacks:add heroku/nodejs
git add . && git commit -m 'ready for prod'
git push heroku main