You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We deploy to and run on Heroku.
That's still the primary move.
But if we have to leave Heroku in some future, we'd like to be able to do that easily and reliably. Docker seems like answer for that.
Heroku even has a Docker story these days. Last time I looked (a year ago), not all of the normal Heroku features worked in Docker offering. It's worth exploring though.
Ultimately, this is about being able to deploy and run the site from a non-Heroku host. That means: AWS, GCP, Azure. But also, homegrown servers. Ideally, both situations would be accommodated by this.
The text was updated successfully, but these errors were encountered:
We deploy to and run on Heroku.
That's still the primary move.
But if we have to leave Heroku in some future, we'd like to be able to do that easily and reliably. Docker seems like answer for that.
Heroku even has a Docker story these days. Last time I looked (a year ago), not all of the normal Heroku features worked in Docker offering. It's worth exploring though.
Heroku + Docker
https://devcenter.heroku.com/categories/deploying-with-docker
https://www.heroku.com/deploy-with-docker
https://devcenter.heroku.com/articles/container-registry-and-runtime
Non-Heroku
Ultimately, this is about being able to deploy and run the site from a non-Heroku host. That means: AWS, GCP, Azure. But also, homegrown servers. Ideally, both situations would be accommodated by this.
The text was updated successfully, but these errors were encountered: