Deploy to Heroku #70
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
Hi, I don't use Heroku personally but it looks like it doesn't let you write to |
Beta Was this translation helpful? Give feedback.
-
I made it. It was some problem us esbuild that was not being installed in production. I reinstalled using rails javascript:install:esbuild and it worked. |
Beta Was this translation helpful? Give feedback.
-
Yes, indeed, it was just wrong configurations from my side. 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. For now I am using only postgresql and redis. The rest is very straightforward. The only catchy thing is the other processes defined in the Procfile. run:
web: bundle exec puma -C config/puma.rb
js:
command:
- yarn build --watch
image: web
css:
command:
- yarn build:css --watch
image: web But I decided not using it and setting the You can see more details about heroku.yml file in here https://devcenter.heroku.com/articles/build-docker-images-heroku-yml Thank you for your attention and support :) |
Beta Was this translation helpful? Give feedback.
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:
So, the service you have in your docker-compose (db, redis, etc) they should be replaced by Heroku's add-ons. Fo…