4 ms·

> There is absolutely no reason or excuse to use docker compose in anything resembling production. I work at a university where I make an app meant for maybe a

> There is absolutely no reason or excuse to use docker compose in anything resembling production. I work at a university where I make an app meant for maybe a couple of concurrent researchers. Am I seriously supposed to set up Docker Swarm for this or is it OK with you if I run my little setup using Docker-compose on the tiny server that the university has provisioned for me? Seriously, why do so many people on HN have to act like the entire world of software developers is busy making the next Facebook? I'm sure many (most?) people are making tiny things meant for tiny audiences.

croon 5y ago
> Seriously, why do so many people on HN have to act like the entire world of software developers is busy making the next Facebook? I'm sure many (most?) people are making tiny things meant for tiny audiences. I agree generally, but playing devil's advocate for GP, what I think they meant is that swarm can be run on a single node with little downside/complexity and a lot of upside from docker compose. See for example: https://jarredkenny.com/single-node-docker-swarm/ https://jarredkenny.com/single-node-docker-swarm/ https://devopstuto-docker.readthedocs.io/en/latest/docker_swarm/articles/2018/01__2018_10_17/01__2018_10_17.html https://devopstuto-docker.readthedocs.io/en/latest/docker_sw...
- simongray 5y ago
  Thanks for the links. I was not aware that it could be run on a single node. Still, the benefits are unclear to me. I guess I will research it some more.
  - rualca 5y ago
    > Still, the benefits are unclear to me. Manage deployments as stacks, which support history and backtrack deployments. Blue-green deployments. Frankly, it boggles the mind how people put to production devtools that are barely managed to be secure when deployed locally, when alternatives are both simpler to deploy and more capable.
    - croon 5y ago
      The charitable assumption is that people use the (best) tools they're aware of. Discovery can be really hard today.
    - simongray 5y ago
      I am in charge of every single thing from devops to data modelling to backend web services to frontend apps to design and testing to responding to inquiries from users of a dozen web services. Does that boggle your mind too? That is the reality of my job. I don't have the time to be an expert in every single area when I am the one who has to do everything. I'm sure you're great at setting up servers. That is probably the part of my job I dislike the most, but it's something I have to do, so I do it.

croon 5y ago

> Seriously, why do so many people on HN have to act like the entire world of software developers is busy making the next Facebook? I'm sure many (most?) people are making tiny things meant for tiny audiences. I agree generally, but playing devil's advocate for GP, what I think they meant is that swarm can be run on a single node with little downside/complexity and a lot of upside from docker compose. See for example: https://jarredkenny.com/single-node-docker-swarm/ https://jarredkenny.com/single-node-docker-swarm/ https://devopstuto-docker.readthedocs.io/en/latest/docker_swarm/articles/2018/01__2018_10_17/01__2018_10_17.html https://devopstuto-docker.readthedocs.io/en/latest/docker_sw...

simongray 5y ago
Thanks for the links. I was not aware that it could be run on a single node. Still, the benefits are unclear to me. I guess I will research it some more.
- rualca 5y ago
  > Still, the benefits are unclear to me. Manage deployments as stacks, which support history and backtrack deployments. Blue-green deployments. Frankly, it boggles the mind how people put to production devtools that are barely managed to be secure when deployed locally, when alternatives are both simpler to deploy and more capable.
  - croon 5y ago
    The charitable assumption is that people use the (best) tools they're aware of. Discovery can be really hard today.
  - simongray 5y ago
    I am in charge of every single thing from devops to data modelling to backend web services to frontend apps to design and testing to responding to inquiries from users of a dozen web services. Does that boggle your mind too? That is the reality of my job. I don't have the time to be an expert in every single area when I am the one who has to do everything. I'm sure you're great at setting up servers. That is probably the part of my job I dislike the most, but it's something I have to do, so I do it.