/r/Homelab /r/HomeServer /r/TrueNAS etc they all exist.
thekrautboy
They are called "personal dashboards" and are easy to find with a simple search of this subreddit, and also you can look at the "aweesome selfhosted" list in the subreddit sidebar, it has a entire section on such dashboards for you.
But uncle joe might have some spyware on his laptop which does it...
If the reverse proxy with high availability doesnt work out for you for whatever reasons, take a look at keepalived as a alternative. You run it on listening on both IPs and once one is detected as being down, the other takes over automatically. Very easy to set up.
iirc techno tim made a youtube video about it some time ago, or someone else, but easy to find i guess.
If yes why ?
Because it makes deploying a bunch of different services like this very simple and reliable to run?
Uhm a "media server" is called a "media server", simple?
A suite or collection of tools is not a "media server".
Its called "yet another media server" but it isnt a media server? But a collection of script to setup *arr stack and jellyfin for example? Sure thats useful to many, its great! But odd namechoice :D
Wow this has never been asked here before.
Struggling to find the usecase for apprise, I think I'm missing something major :D
Just from 2 days ago: https://www.reddit.com/r/selfhosted/comments/17ffx39/eli5_apprise/
How can I receive messages on multiple different channels (smtp, webhooks, maybe syslog etc) and send via smtp (or something else I choose in the future).
I would use n8n for that, you can feed almost anything as input to it, and output it as almost anything. Similar tools are automatisch and activepieces.
Often for people who ask this kind of question things like /r/CosmosServer or CasaOS are ideal as first step.
But you could simply search this sub because this exact post has been made countless times already.
Look at personal dashboards that have user accounts, check the awesome selfhosted list in the subreddit sidebar.
https://github.com/Red5d/docker-autocompose
For the future you should get started by using compose files from the beginning, and keep those as your "backup" of the container config. Exporting them from a deployed container is not the intended approach.