3 ms·

It doesn't, no. I don't even know what that is (well a quick look at the documentation: it's about Docker, which is not needed for Heroku). All it requires is

by Fradow 4y ago

It doesn't, no. I don't even know what that is (well a quick look at the documentation: it's about Docker, which is not needed for Heroku). All it requires is a Procfile, which can contain a single line telling how to start your server and that you can extend to add other process types. It's not even needed for simple apps.

yunwal 4y ago
Genuine question, is a Procfile really that preferable to a Dockerfile with equivalent functionality? > cmd: python helloworld.py doesn't seem massively less complicated than FROM alpine CMD ["python", "helloworld.py"] FWIW, I've never used heroku in production so maybe it's more about the constraints of heroku than the number of words, but it just doesn't seem like a huge deal to me.
- ek750 4y ago
  I'm familiar with docker but certainly not an expert, so this is surprising to me. Is it really possible to have a single line dockerfile? The smallest one I've used was probably a screen full, due to updating packages, setting up bundler paths, etc. A production dockerfile is much larger with non-root user shenanigans, etc. But to answer your question about Heroku, a Procfile is much smaller and more constrained in scope than a Dockerfile.
  - girvo 4y ago
    > I'm familiar with docker but certainly not an expert, so this is surprising to me. Is it really possible to have a single line dockerfile? Not single line, but two lines, sure. Though you're at the mercy of your upstream image and how it configures things. Though I guess that's also true of buildpacks. Plenty of my Dockerfiles are no more than a couple lines. Heroku was still nicer in most ways of course, at least in my opinion.
- Fradow 4y ago
  Since I've never used Docker, I can't answer. A Procfile works well with what you'd want to do on Heroku: run a webserver, and maybe run some other worker process. It's a single line per process, equivalent to what you run locally.

by Fradow 4y ago

yunwal 4y ago

Genuine question, is a Procfile really that preferable to a Dockerfile with equivalent functionality? > cmd: python helloworld.py doesn't seem massively less complicated than FROM alpine CMD ["python", "helloworld.py"] FWIW, I've never used heroku in production so maybe it's more about the constraints of heroku than the number of words, but it just doesn't seem like a huge deal to me.

ek750 4y ago
I'm familiar with docker but certainly not an expert, so this is surprising to me. Is it really possible to have a single line dockerfile? The smallest one I've used was probably a screen full, due to updating packages, setting up bundler paths, etc. A production dockerfile is much larger with non-root user shenanigans, etc. But to answer your question about Heroku, a Procfile is much smaller and more constrained in scope than a Dockerfile.
- girvo 4y ago
  > I'm familiar with docker but certainly not an expert, so this is surprising to me. Is it really possible to have a single line dockerfile? Not single line, but two lines, sure. Though you're at the mercy of your upstream image and how it configures things. Though I guess that's also true of buildpacks. Plenty of my Dockerfiles are no more than a couple lines. Heroku was still nicer in most ways of course, at least in my opinion.
Fradow 4y ago
Since I've never used Docker, I can't answer. A Procfile works well with what you'd want to do on Heroku: run a webserver, and maybe run some other worker process. It's a single line per process, equivalent to what you run locally.