shiftymccool

I'm using Kopia with AWS S3 for about 400GB and it runs a bit less than $4/mo. If you set up a .storageconfig file it will allow you to set a storage level based on the file names. Kopia conveniently makes the less frequently accessed files begin with "p" so you can set them to the "infrequently accessed" level while files that are accessed more often stay in standard storage:

{
  "blobOptions": [
    {
      "prefix": "p",
      "storageClass": "STANDARD_IA"
    },
    {
      "storageClass": "STANDARD"
    }
  ]
}

I've been using OneDev. It's really easy to set up, kinda just works out of the box

Are these western chauvanists in the room with us right now?

As of now, it's just one person getting some clarity on the definition of poverty from another person and you. You must really want to peddle your paywalled links because that's quite the comment hair-trigger you got there

Elon's wet fucking dream

I use it in a homelab, I don't need to apply prod/team/high-availability solutions to my Audiobookshelf or Mealie servers. If an upgrade goes wrong, I'll restore from backup. Honestly, in the handful of years I've been doing this, only one upgrade of an Immich container caused me trouble and I just needed to change something in the compose file and that was it.

I get using these strategies if you're hosting something important or just want to play with new shiny stuff but, in my humble opinion, any extra effort or innovating in a homelab should be spent on backups. It's all fun and games until your data goes poof!

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 ¯\_(ツ)_/¯

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

Oh no, they might have to flip over another couch cushion to find that kind of money

...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

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