3 ms·

Almost all my apps get deployed to Heroku, both professionally and side projects and I opt to use the Heroku Stack instead of deploying my own docker image on H

Almost all my apps get deployed to Heroku, both professionally and side projects and I opt to use the Heroku Stack instead of deploying my own docker image on Heroku. Even though I use docker locally. One of the main reasons is that Heroku's "Stack" is updated monthly (sometimes more frequently if there are security issues). You don't get this when you deploy docker to Heroku. https://devcenter.heroku.com/articles/stack-update-policy https://devcenter.heroku.com/articles/stack-update-policy

arusahni 6y ago
The double-edged sword here is that you can get hit by their stack retirement policies. Cedar-14 was killed this year, and Heroku-16 is gone next year. For better or for worse, Docker images will continue to run.
- FemmeAndroid 6y ago
  I deal with this, but they do let you know far ahead of time, and they don't seem to stop existing dynos from running even after a stack is retired. So I now just get a nice, clear message on one long running application I haven't taken the time to update (or more likely, wind down.) "This app is still using the cedar-14 stack, for which the end-of life window has closed as of November 2nd, 2020. The cedar-14 stack will no longer receive security updates and builds will be disabled for apps running on the cedar-14 stack."
  - londons_explore 6y ago
    One day they'll have to shutdown old dynos... Either because it's no longer compatible with their systems, or because there is some wormable vulnerability...
    - FemmeAndroid 6y ago
      I mean, this is true in the same way it's true that some day you'll have to shutdown old images running on docker though. I'm just trying to point out that it's not like they are quick to shut down working processes, and even weell after they EOLed an old bit of tech, and nagged me to update it for over a year, it's not stopped working yet.
  - arusahni 6y ago
    They prevent you from starting a new stack. I had automation that spun up new stacks for automated testing. That all broke.

arusahni 6y ago

The double-edged sword here is that you can get hit by their stack retirement policies. Cedar-14 was killed this year, and Heroku-16 is gone next year. For better or for worse, Docker images will continue to run.

FemmeAndroid 6y ago
I deal with this, but they do let you know far ahead of time, and they don't seem to stop existing dynos from running even after a stack is retired. So I now just get a nice, clear message on one long running application I haven't taken the time to update (or more likely, wind down.) "This app is still using the cedar-14 stack, for which the end-of life window has closed as of November 2nd, 2020. The cedar-14 stack will no longer receive security updates and builds will be disabled for apps running on the cedar-14 stack."
- londons_explore 6y ago
  One day they'll have to shutdown old dynos... Either because it's no longer compatible with their systems, or because there is some wormable vulnerability...
  - FemmeAndroid 6y ago
    I mean, this is true in the same way it's true that some day you'll have to shutdown old images running on docker though. I'm just trying to point out that it's not like they are quick to shut down working processes, and even weell after they EOLed an old bit of tech, and nagged me to update it for over a year, it's not stopped working yet.
- arusahni 6y ago
  They prevent you from starting a new stack. I had automation that spun up new stacks for automated testing. That all broke.