Conversation

Notices

1. Embed this notice
   受不了包 (shibao@misskey.bubbletea.dev)'s status on Tuesday, 19-Mar-2024 02:28:48 JST 受不了包

   i haaate multiple compose files can people please stop I don't care that you have multiple extends and shit if that's supposedly the "better" way it's just so much extra complexity for no goddamn reason just put your fucking config in a single yml file for the love of god
   .env files are on thin fucking ice, compose override files are absolute trash because they rely on the original yml file anyways so there's no fucking reason to separate it out
   this has been a psa to not be stupid

   • Embed this notice
     受不了包 (shibao@misskey.bubbletea.dev)'s status on Tuesday, 19-Mar-2024 02:37:12 JST 受不了包

     in reply to

     • pry

     @pry@raru.re it's like the clean code thing where you read "use atomic tiny functions for everything" and immediately want to use 10 billion functions and then have to rewrite all the code from that fad 6 months later because it's completely fragmented and indecipherable instead of just writing plain, non-magic functions that might have a bunch of lines but don't have a billion branching items that you have to switch off to understand what they're doing so you can figure it out
     docker compose overrides are just this problem except people who have never had to go through a clean code hell though
     idk i was never really susceptible to the clean code function thing but tons of people have done it

   • Embed this notice
     pry (pry@raru.re)'s status on Tuesday, 19-Mar-2024 02:37:14 JST pry

     in reply to

     @shibao but like... is it really that much complexity added for being more organized?

     I only run like 3 or 4 services so it doesn't make sense for me but when I look at the amount of services some people run, I feel like splitting it up does make sense

   • Embed this notice
     受不了包 (shibao@misskey.bubbletea.dev)'s status on Tuesday, 19-Mar-2024 02:46:25 JST 受不了包

     in reply to

     • pry

     @pry@raru.re it's even worse because i don't need to go through a docker-compose.yml to an extends: section which refers to another random-partial-configs.yml file and then you go into that and realize it has a custom shorthand that just adds like enable-vaapi: devices: - /dev/dri:/dev/drithat gets injected when you do this my-service: # blah blah other stuff extends: file: ./additional-overcomplicated-config-dir/random-partial-configs.yml service: 'enable-vaapi'when you could literally do my-service: # blah blah other stuff devices: # - /dev/dri:/dev/dri # Uncomment to enable vaapiin the config, bam no need to dig through multiple yml files for a tiny config change
     maybe if it were a pretty complex config change it might be warranted but then in that case you should stop doing code as configuration as much as feasible if it were a developed app, but literally just doing this for a standard config is almost inexcusable for basically one line changes...
     basically i hate overcomplicated devops, just make your shit as simple as possible