Hey everyone! I'm sort of still green for selfhosting, but I wanted to share my setup so far:
The following services are selfhosted in docker
- Audiomuse (smart music tagging, mood based and all that)
- Navidrome for music hosting
- Jellyfin for TV shows (not a lot) and Films (not a lot again, but steadily increasing)
- Radicale for serving contacts/TODOs/calendar
- SFTPGo to act as my drive
- Kavita for ebooks and manga (I have tons of both)
- Glance for homepage
- forgejo for git forge hosting
The system specs are kind of visible in the homepage, so I won't spell them out here again. Mostly an old optiplex running arch, though I want to change it to nixos later on.
System tools:
- nushell for shell
- calibre for ebook management and tagging + fanficfare plugin to download fanfictions
- Caddy for reverse proxy (so I don't have to remember ports)
- netbird for VPN (also because it allows me to set wildcard DNS resolution for nodes, so I don't have to set up a dedicated pi-hole or adguard)
- Handbrake and ffmpeg for processing videos and such
- beets for tagging music
- a sysinfo script to generate system information for glance to consume
- Probably other things too, I'm forgetting
Everything is accessible only via netbird, and external inbound connections are firewalled off
Apart from that, I eventually plan on adding the following as well:
- Immich for photo hosting
- Vaultwarden for passwords
- Gollum (still debating on alternatives) for a webUI for my notes
- Paperless-NGX
I'm still thinking on more that I can add. Note that whatever I add should not need an inbound connection/stable IP address, since I don't intend to expose the server to the public. Any suggestions/tips? Thanks!
UPDATE: Forgot to add, I'd probably add homebox too, for inventory management ๐
UPDATE 2: I'm silly, I forgot that I'm also looking into self-hosted RSS feed readers ๐
Awesome! I have a very similar setup to you. I recommend installing pi-hole regardless and putting at least Hagezi's normal block list on it, just for a sane web browsing experience.
Home Assistant is also really good, because it includes a bunch of stuff that you probably wouldn't first think of. For instance, I'm using its API to request the indoor temperature from my home thermostat and the outdoor temperature from a weather module that it has built in, and I've programmed it to let me know when it's too hot to walk the dog, and when to open/close the windows in the house to keep it as cool as possible in this heatwave.
I'm using LeafWiki for home documentation. A list of things I intend to try hosting, my backup strategy which I'm bound to otherwise forget. I'm thinking about putting all of our meals on there so that we when we get tired of a particular meal for a while, we can return to it when we're at a loose end with the shopping.
I'm checking out LeafWiki. Thanks for that.
Oh wow! I didn't know home-assistant can work in a closed network, but now it makes sense
What does leafwiki do exactly?
I also read your backup strategy below and that seems pretty interesting. My strategy differs. Have nothing in the volumes, unless it's like docs or whatever lol. I do think that'll change with things like Paperless, since I'd want to persist and carry over the tagging strategy or whatever.
It just allows you to quickly make pages of content, like Wikipedia. It has a tree navigation and search. Here's a demo site: https://demo.leafwiki.com/home
Ah, it seems that gollum would cover this, although I'd keep an eye on this as well.
Leafwiki website looks like ai slop
How do you do backups and what's the codeberg service?
I keep my container volumes in sub-directory of that of the docker compose file and tar them up and put them somewhere safe. I spent ages trying to figure out how to back up a container, because I thought that the state of a database was in memory, which I suppose it is, but when you stop it, it's just a bunch of files like everything else, so I elected to keep it simple. I've been thinking of creating a cron job to do it routinely. I'm not sure what you mean regarding the codeberg question.