Prod heroku #2
Merged
Prod heroku #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is working for the main web process in Heroku. Here are some
caveats:
- Forced to add a dummy ACTION_CABLE_ALLOWED_REQUEST_ORIGINS env variable to
Dockerfile.web to make the repcompile task run successfully because
config/application.rb assumes it has a value (invokes split)
- Manually added the following variables to Heroku:
- SECRET_TOKEN=`rails secret` (or heroku config:set
SECRET_TOKEN=`docker-compose run --rm
website rails secret`)
- ACTION_CABLE_ALLOWED_REQUEST_ORIGINS=`heroku apps:info | grep "Web
URL:" | sed -e 's/^Web URL: //'`
- Other sub-processes/resrouces to still be tested:
- ActiveMail - SMTP
- ActiveJob - Redis
- ActionCable - Redis, CORS
- Cache - Redis
This makes it easier to use the PORT env that Heroku sets automatically. *The main web dyno was running in Heroku at this commit.* However, the assests were 404ing: > Failed to load resource: the server responded with a status of 404 (Not Found) https://superrandomdomain.herokuapp.com/assets/application-85cc27dda36172aa13df3b2a8ce284c375a233606df823c56c23e15915ba7ba0.css I fixed by manually setting the environment variable: RAILS_SERVE_STATIC_FILES=true - Other sub-processes/resrouces to still be tested: - ActiveMail - SMTP - ActiveJob - Redis - ActionCable - Redis, CORS - Cache - Redis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This contains a production-specific Docker build. The main web Dyno process works including:
STDOUTwebi.e.heroku container:push web --recursiveI was unable to get the orats base
Dockerfileto work out of the box in Heroku. Here's a summary of what I had to do to get things working in production/Heroku:config/puma.rbto assume the IP address forbindbut require thePORTenv variable which Heroku sets automaticallySee the commit messages for more details.
Futures
Ideally, I'd like to get a single
Dockerfilethat could be used in all environments.Both commits mention:
I am going to merge this PR anyway so I can test pushing features changes to production. I will defer these to #3.
Resources
https://github.com/nickjj/orats
Rails + Docker
https://devcenter.heroku.com/articles/container-registry-and-runtime
https://nickjanetakis.com/blog/dockerize-a-rails-5-postgres-redis-sidekiq-action-cable-app-with-docker-compose
https://dzone.com/articles/deploying-your-docker-rails-app
https://blog.red-badger.com/blog/2016/06/22/docker-and-assets-and-rails-oh-my
Rails + Heroku
https://blog.heroku.com/real_time_rails_implementing_websockets_in_rails_5_with_action_cable
https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#port
https://blog.heroku.com/container_ready_rails_5
Docker
https://www.digitalocean.com/community/tutorials/how-to-remove-docker-images-containers-and-volumes