

I guess I don’t get that granular. It will respect the current docker compose image path. So. if you have the latest
tag, that’s what it will use. Komodo is a big topic: https://komo.do
I guess I don’t get that granular. It will respect the current docker compose image path. So. if you have the latest
tag, that’s what it will use. Komodo is a big topic: https://komo.do
Not sure why Renovate is necessary when Komodo has built-in functionality to update Docker images/containers. I wish there was an option to check less often (like once a day), maximum time is hourly.
Also, if you’re using Komodo and have one big repo of compose files, consider just saving your entire config toml to a repo instead. You end up with something akin to Terraform or Cloudformation for your Docker hosts
It’s almost like punctuation was made for a reason…
I, apparently, have the pleasure of introducing you to Cave Johnson: https://youtu.be/NyLUU3O4zW8?si=FQy2MbPEy2_xEzzG
Oh no, they might have to flip over another couch cushion to find that kind of money
I used nextcloud for a while but ended up with a combo of syncthing and filebrowser to similar effect
Multiple sag layers? What is this, the early 90’s?
You’re the reason we can’t have nice things
…to understand Donald Trump…
I’ll just stop you right there, nobody needs this
In this case, it appears that Gmail’s AI search tool will be optional.
Until they quietly turn it on by default after the initial news had cooled down
The LLM generates software, freeing the programmer from having to write and debug the underlying code
Aaaaand this is the problem. Sure, go ahead and let the slop machine generate the code, but you definitely have to debug that shit.
It’s really the same definition. The first time i heard it in this context was with modding/rooting smartphones (in the early days). If you fucked up a step, your device could end up in a completely unusable and unrecoverable state. At that point, its only use would be as an expensive brick
People sure like to just toss the word “brick” around. These printers are still functional enough to get another firmware update to fix them. You know what can’t? Bricks
Kärcher is awsome, all of their products I have are solid and dealing with the company is ridiculously easy. They always have parts on-hand and repairs are usually a handful of steps. Easy recommendation
My home network is called The IT Clowd with these devices:
Is almost like rampant breeding without any environmental pressures causes a decline in the traits that evolved to deal with those pressures. AKA, Idiocracy has happened because we’re too soft to tell people to stop fucking. “Having babies is a Gawd-given right! You can’t take away muh freedums!” Most people shouldn’t be breeding, the species weeps when ~90% of us give birth.
Looks are somewhat similar but 🤷♀️
It’s a straight up copy. Somewhat similar… JFC
Looks just like Arc
Komodo is a big topic so I’ll leave this here: komo.do.
In a nutshell, though, all of Komodo is backed by a TOML-based config. You can get the config for your entire setup from a button on the dashboard. If have all of your compose files inline (using the editor in the UI) and you version control this file, you can basically spin up your entire environment from config (thus my Terraform/Cloudformation comparison). You can then either edit the file and commit, which will allow a “Resource Sync” to pick it up and make changes to the system or, you can enable “managed mode” and allow committing changes from the UI to the repo.
EDIT: I’m not really sure how necessary the inline compose is, that’s just how I do it. I would assume, if you keep the compose files in another repo, the Resource Sync wouldn’t be able to detect the changes in the repo and react ¯\_(ツ)_/¯