4 ms·
I didn't know Heroku offered that service. In any case, my question was really about source vs containers. The nice thing about the former is most of the infras
by _bxg1 7y ago
I didn't know Heroku offered that service. In any case, my question was really about source vs containers. The nice thing about the former is most of the infrastructure is taken care of for you, so you don't need a devops person or a docker workflow.
- duxup 7y agoI suspect Heroku is pretty much fine. As the other poster noted it has a system setup that is really stable, and probabbly is efficient to run. Maybe not the most wiz bang / get the attention more complex deployments have, but I suspect it is heavily used.
- th3ch073n1 7y agoYou could also check out https://render.com/ https://render.com/ . I personally prefer it to heroku and they have amazing support for containers as well. It kind of gives you the advantages of both IaaS and PaaS at the same time
- photonios 7y agoThere are actually two ways to do Docker with Heroku. You can let Heroku build your image during the deployment phase by simply having a `Dockerfile` in your repository [1]. Or, you can build the image yourself on your CI service and push it to Heroku's registry and then trigger a release. This last option is useful if you want to run tests against the exact image that is going to be deployed without having to rebuilt it [2]. [1] https://blog.heroku.com/build-docker-images-heroku-yml https://blog.heroku.com/build-docker-images-heroku-yml [2] https://devcenter.heroku.com/articles/container-registry-and-runtime#building-and-pushing-image-s https://devcenter.heroku.com/articles/container-registry-and...