Hmmm, definitely a grey area in my mind especially with the definition of "host". The host is where the software lives and that isn't yours. Maybe self-managed?
Ho... Ly... Shit... This is great! The UI is a bit confusing at first but doesn't take long to get what's going on. I might even be disappointed with a UI revamp 😁 I can't believe how much functionality this has. It's already replacing some processes I have for mounting drives and backing up files. Maybe I missed something, but my only complaint would be the lack of an automatic one-way folder sync in the Party UP! app.
I use Forgejo mostly for code archiving but anything that requires CI/CD, like personal code projects, i use OneDev. No extra setup for pipeline, batteries included
A brick is a brick. It can be used to make a wall or hold paper down. That brick will never "wake up" and become more than a brick. A brick is not soft. A brick is not temporary. If you have a brick, it does not and will not ever work for anything except masonry.
The word "literally" has real meaning and so does the concept of a "brick" in electronics. These things are immutable. Do not change the meaning of "immutable".
Not sure if this will work for you but I keep my homelab documentation in markdown, mainly edited with Obsidian. I wanted an easy way to access via web and found Perlite. I have this pointed at a notes folder on my server which is auto-updated with Syncthing. No fuss, just works
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:
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 ¯(ツ)_/¯
Hmmm, definitely a grey area in my mind especially with the definition of "host". The host is where the software lives and that isn't yours. Maybe self-managed?