That's a great point about Ansible. Compose automates most of the setup, but automating all of it would be amazing. I'll try it with the next service I set up, and if it goes well, I'll document it. Thanks for the suggestion!
I am familiar with tunnels in general, though I haven't seen Cloudfare's offering. I'm with the sibling comment that it's another external dependency when my goal is to self host more. But that's a tool I'll keep in mind!
I'll have to check out Caddy plugins! One I saw called the docker command to discover exposed ports, meaning it depends on Docker explicitly. I'll see what I can dig up wrt Podman. This sounds very interesting. Thanks!
Great suggestion! Someone else also suggested Ansible, so I'll try it for the next service I set up. If it works out, I'll publish another post on my experience :)
I don't do a great job of this, but take Immich for example. There, I specify the version in the compose.yml (technically, the version is in the .env file and substituted into the compose.yml). At that point, updating Immich is a matter of updating the version number and restarting the service.
These configuration files are all managed with git, so when I do these updates, I create a new commit. I just checked, and I have Forgejo pinned to a specific version in its compose.yml as well. But unfortunately, the other services are referencing :latest. I'm going to go back and pin them all :)
It lets you clear the bash command history, either completely or selectively. Here's the GNU docs for the history builtin: https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html#index-history
(I'm not too familiar, someone else can clarify: is this available outside bash?)
What's interesting to me is the
-aoption, which lets you "flush" the history for the current session without ending the session. I can see that being useful!