I see. That is a valid concern. Though it feels unfair to say that headscale is ‘made by a tailscale employee’. From what I understand, one of the main contributors of headscale was hired by tailscale, though he is not the only maintainer and does not own the repo from what I can tell. Still, Tailscale could decide to cede all support of headscale and that would likely hurt the project a lot. In the same way however nebula could decide to switch to proprietary licenses and discontinue their open source offerings.

What made you choose Nebula over Tailscale? I’m running it through a self-hosted Headscale server and it’s working well so far. I haven’t looked into Nebula too much.

As long as your apt sources (/etc/apt/sources.list) are set to bullseye (and not eg. stable) you won’t “accidentally” upgrade to bookworm. At least that’s how it works in Debian, I assume raspbian is the same.

Don’t you have to download episodes to your server first in ABS? That makes it useless for me as a podcast app.

Looks and sounds very promising! I’ve been looking for a self-hosted podcast server that I can use to sync podcasts and progress between multiple devices. Nextcloud Gpodder sync is already great, but there does not seem to be any iOS app that supports it. So I’m really looking forward to seeing more of your project!

In Jellyfin you can create as many distinct music libraries as you want. The normal client isn’t amazing for listening to music, but on android there is finamp

For android there is Finamp, a music-focused jellyfin client app

To put it in simpler terms, I’d say that containers virtualise only the operating system rather than the whole underlying machine.

I guess not then.

I recently switched from etesync to a self-hosted solution and didn’t want to install a full Nextcloud on my tiny home server just for that. So I initally tried out radicale as well, but I didn’t like the default user handling (no authentication at all) and the project had been unmaintained until very recently (two weeks ago). I switched to baikal then and I am quite happy with it so far.

Containers are useful for a lot more things than scaling. E.g. portability, ease of setup, dependency separation.

Keepass2Android handles that pretty well. It checks for external changes to the remote database before every local edit. And the desktop nextcloud app notices conflicts as well and can create a second version of the file if there are conflicts. You can then check for the differences with something like keepass-diff. But that should only happen if you change your db without syncing first, so while you are offline or the nextcloud app wasn’t running.

Keepass2Android implements syncing in a way that actually works. I sync through my nextcloud instance. On my laptop it’s just KeepassXC and the nextcloud desktop app, on my mobile (android) devices Keepass2Android. On iOS I think there was Strongbox but I haven’t used it in a long time. I tried using KeepassDX with the nextcloud android app for syncing for a while, but it lead to regular silent sync conflicts including password losses.

I think kavita works fairly well. It doesn’t have an app, but it comes with a built-in OPDS server, so you can just plug the link into any app that supports it and access all your book. For eink devices I recommend koreader. For other devices you may prefer an app with a less confusing UI, but that’s a matter of preference. Alternatively the kavita webclient has a reader as well.

Yep, haven’t tried Jellyfin for audiobooks in a while, but when I did it didn’t work well. Audiobookshelf on the other hand is really really good.

I don’t know how well the Jellyfin app for xbox works, but you can also install Kodi with the jellyfin addon I think. Or share your library via smb and connect to that directly with Kodi.

That sounds like a super inconvenient way of doing it

I’m not aware that progress saving is a default feature of OPDS. There is some work being done in that direction, but I don’t know of any server/app combinations that do that for ebooks. Apart from that, I’m relatively happy with kavita. It comes with a web UI though.

To be honest, I would advise against opening your home network like that at all. A VPN would be much safer. If you use something like Tailscale it would be much easier as well and doesn’t need opening any ports at all.

I recommend going with regular backups and maybe something like docker. Then you just have to restore the config volumes and all the accounts should still be there.

Why do you use SMB instead of just connecting to the different jellyfin servers directly via VPN?