Having the ability to shut down the main instance of an app and run a secondary instance from backups without much hassle is the best feeling ever, I recently updated from Nextcloud v26 to v31, and having the ability to just go back to a working version if anything was wrong saved me from so much stress.
Yeah, these are pretty solid advice, would say that you should be safe with patch version updates, like from 1.17.1 to 1.17.4
Should be able to jump from 1.17.4 to 2.0.1 and from 2.0.1 to 2.1.3, etc. going straight to the last patch of the next version, but should go one by one minor version, paying close attention to those versions that have breaking changes in the release notes. And always backup and test before each version jump.
This probably is the issue, when you download a script or binary from the internet it doesn’t have execution permission, you would have to right click on folder to open in terminal (that way don’t have to cd to it), and check permissions with ls -la if it doesn’t have permission, change it with chmod
In my mind it would be super useful, I could sync my photos when my PC is on and when is off rely on my local photos only since my main goal is having a backup of them.
You could do this perfectly with the docker version, so just curiosity here, why not user docker?
Is it because you don’t want to install docker for only Immich? (you could also install other selfhosted server/apps as bonus),
would you be against snap? As someone already mentioned, there is a snap version.
If the important thing is having backups of your photos, there are alternative apps with different packaging formats.
You could make a request for flatpak, and see if other users also would like it, but you would have to wait for feedback from devs and understand if they don’t have the resources or willingness to maintain it.
Am I crazy or it makes sense?
If I’m interested in a specific app, I see what packaging formats it has and see how to install it and try it out. Only if I’m having issues with it (that can’t be solved), or can’t run it on my specific distro with the available packaging formats, I try to suggest/request a different format.
As far as I know, CasaOS (same as Cockpit) is installed on top of a default OS install, so you could always access the OS directly to install/configure things outside of it, if the need arises.
I would not say you would be held back by it, if it does what you need. And for what I can see online, you can install any docker container even if it’s not on the default catalog of CasaOS, or access the OS.
If you want to grow your knowledge of how things work, or how to deploy services without CasaOS, you can always do so in parallel of using CasaOS, so I don’t see where the issue could be.
Used Gitea for a while, and decided to switch to Forgejo before the hard fork split (no more code from Gitea), been using it since, In my opinion both work well, but prefer Forgejo.