Skip to content

Deploy to Heroku #70

Answered by paulofabiano
paulofabiano asked this question in Q&A
Oct 10, 2023 · 3 comments · 5 replies
Discussion options

You must be logged in to vote

Yes, indeed, it was just wrong configurations from my side.
Well, with your setup, the best option to deploy was migration my stack to container instead heroku-22 (heroku stack:set container) and defining a heroku.yml file, which basically acts as a docker-compose.yml.
Mine is like this:

setup:
  addons:
  - plan: heroku-postgresql
    as: DATABASE
  - plan: heroku-redis
    as: REDIS
  config:
    REDIS_TLS_URL: ...
    REDIS_URL: ...
    SECRET_KEY_BASE: ...
build:
  docker:
    web: Dockerfile
  config:
    RAILS_ENV: production
run:
  web: bundle exec puma -C config/puma.rb

So, the service you have in your docker-compose (db, redis, etc) they should be replaced by Heroku's add-ons. Fo…

Replies: 3 comments 5 replies

Comment options

You must be logged in to vote
3 replies
@paulofabiano
Comment options

@nickjj
Comment options

@paulofabiano
Comment options

Comment options

You must be logged in to vote
1 reply
@nickjj
Comment options

Comment options

You must be logged in to vote
1 reply
@nickjj
Comment options

Answer selected by nickjj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants