3 ms·

Why is docker compose a red flag? That feels like a benefit to me.

by tootie 1y ago

cowmix 1y ago
100% -- firs time I have seen providing a docker compose file is a sign of weakness.
tracker1 1y ago
Yeah... I'm not sure that I've ever seen a complex app with multiple, separate service/database requirements (redis, pg, etc) packaged in a Linux distro repository... but I could be wrong.
- dingnuts 1y ago
  controversial but docker compose is for development and demos. for prod give me a binary, a config file / systemd unit file, and tell me how to configure external dependencies and let me decide how to manage them. and if you're serious, k8s config. otherwise don't waste my time.
  - tootie 1y ago
    But this is for running on an old PC in your closet next to your router. Not serving 40k concurrent users. I would not even consider trying to scale it past a dozen family members. And anytime I run an upgrade or config change I just do it in prod.
  - tracker1 1y ago
    You can get all that information from a compose file.
  - pkulak 1y ago
    Waste your time? You know what would waste my time? Building out my own deployment of Redis/Postgres, all the dependencies, systemd services, ML server, and backup solutions (yes, the compose takes regular DB backups for you) and then keeping it all updated manually, just to host photos on my local network for my family of 4. Do you think making your life needlessly difficult is a feature? Then read the docs and deploy to a K8s cluster. Nothing is preventing you from doing that.
rlpb 1y ago
It's not a problem that Docker Compose can be used and a configuration is provided. What's an indicator of a dependency problem is when it's the only way to deploy the software. If, instead, they could say "all required dependencies ship in Debian at a sufficient version to meet our requirements" then that would be ideal (Debian isn't a hard requirement for me, but I use it as an example since it sets a bar similar to the one I want software I deploy to meet). Or even just "nearly all dependencies except this one" would be much better.

Why is docker compose a red flag? That feels like a benefit to me.

by tootie 1y ago

Why is docker compose a red flag? That feels like a benefit to me.

cowmix 1y ago

100% -- firs time I have seen providing a docker compose file is a sign of weakness.

tracker1 1y ago

Yeah... I'm not sure that I've ever seen a complex app with multiple, separate service/database requirements (redis, pg, etc) packaged in a Linux distro repository... but I could be wrong.

dingnuts 1y ago
controversial but docker compose is for development and demos. for prod give me a binary, a config file / systemd unit file, and tell me how to configure external dependencies and let me decide how to manage them. and if you're serious, k8s config. otherwise don't waste my time.
- tootie 1y ago
  But this is for running on an old PC in your closet next to your router. Not serving 40k concurrent users. I would not even consider trying to scale it past a dozen family members. And anytime I run an upgrade or config change I just do it in prod.
- tracker1 1y ago
  You can get all that information from a compose file.
- pkulak 1y ago
  Waste your time? You know what would waste my time? Building out my own deployment of Redis/Postgres, all the dependencies, systemd services, ML server, and backup solutions (yes, the compose takes regular DB backups for you) and then keeping it all updated manually, just to host photos on my local network for my family of 4. Do you think making your life needlessly difficult is a feature? Then read the docs and deploy to a K8s cluster. Nothing is preventing you from doing that.

rlpb 1y ago

It's not a problem that Docker Compose can be used and a configuration is provided. What's an indicator of a dependency problem is when it's the only way to deploy the software. If, instead, they could say "all required dependencies ship in Debian at a sufficient version to meet our requirements" then that would be ideal (Debian isn't a hard requirement for me, but I use it as an example since it sets a bar similar to the one I want software I deploy to meet). Or even just "nearly all dependencies except this one" would be much better.