agilgur5
commented
6 years ago And as of Oct. 2017, Heroku officially supports Docker! https://blog.heroku.com/container-registry-and-runtime
As I still have permission to access the Heroku app, I've updated it to use the current version of the codebase w/ Docker. I believe this also means it's running thru my free dyno hours on Heroku instead of the VRRG's, which really should be adjusted... :/ The Heroku app is still linked in the README and the GitHub link (which I don't have permission to change), so this makes that link once again useful instead of confusing / deprecated. The VPS link also didn't seem to work anymore, so this means there is an actual live and up-to-date version hosted online somewhere.
To deploy to Heroku, I:
- made a production build of LTLMoPWeb3D
- In the
app/folder, ranheroku container:push web --app ltlmop(per the Heroku Container Registry Deployment directions, after logging in to Heroku and the Registry)
Maybe the docs should be updated for this, but as this project has been pretty much deprecated the past few years ¯_(ツ)_/¯
So Docker can't really run on Heroku. Heroku's docker plugin is to assist developing your production app locally (to increase dev/prod parity). It then pushes a Heroku slug from the container for deployment. I thought I could create this slug myself by using my own container based off Cedar (as Heroku recommends)... BUT the slug requires everything be installed in the app folder and self-contained there so that it is essentially a standalone runnable that can be tar'd and gzipped. This essentially ruins the point of using Docker... so that was scratched.
As Heroku is both annoying and is actually hindering dev/prod parity, really would like to move to AWS. ECS should be great for this and pretty sure free tier covers 3 VMs (way more than enough). Azure's research credits should probably work with this as well if someone wants to use Azure. SoftLayer is probably similar. But let's stick with AWS since it's better and more familiar.