It uses the Calibre database but isn’t a frontend per se. With care, you could share the db between the two, and just call up the desktop version when dedrm is needed. There’s also a docker mod with the LSIO container but I think it only supports format conversion.

Eh, there’s something to be said for experimental periods in my view. Sometimes you try out new programs that you wouldn’t think would be useful but end up becoming essential. And then culling mercilessly anything that turns out to be not useful, or overly complex to maintain, reducing your maintenance burden.

I use it with apprise and mailrise (email interface over apprise) typically. Apprise is basically a generic notification sender that can send push notifications to a bunch of different clients, including gotify.

So, things like Proxmox errors get set to a fake mailrise address -> apprise -> gotify. And a lot of Linux apps in general (especially older ones) only support email notifications, so this is quite useful. You can also use apprise directly, even as a commandline interface. So you can make scripts to notify you of problems in cases where there isn’t already proper logging and notification support.

And I’ve setup diun to give me notifications for docker version updates. In this case, diun sends notifications to gotify directly.

Compared to other embedded devices, ease of installation, less chance of driver quirks and much higher performance (especially relevant if you’re running a VPN on the same device).

Compared to other x86 software based routers, a UI that is familiar, and the Linux kernel which generally means it gets new features quicker than its BSD based counterparts.

The only thing I don’t like about caddy is that using DNS challenge requires recompiling the program itself, and the plugins themselves can be a bit quirky. Mind you, you can easily handle this with a separate program like lego or certbot so not a huge deal.

I personally backup my phone to my own USB stick every few days or so

Is that automated? It sounds kind of tedious, and it would be easy to lose data if something goes wrong in between those few days.

Some of the motivation behind self hosting is that there is one source of truth that is easy to manage and make backups for (a server or servers). Android backups in particular are kind of notoriously fragile (especially if you’re avoiding Google services) so it’s simpler to have the data stored on a server. Then I can wipe or lose my phone with impunity without really worrying about losing data, because it’s handled elsewhere.

Nevertheless, you might like the idea of local-first software which is kind of a hybrid between local only software, and self-hosting (or cloud hosting).

think most people do unless you run a DNS server.

Or you access Navidrome from inside a VPN.

Not something so complex that it requires docker. Not something that requires you to install a separate database. Not something that depends on redis and other external services.

This comment is a bit silly. Databases just make sense for many services, although many could just use sqlite which would be fine (and many do). Redis etc is usually optional and might increase performance in some cases.

I wouldn’t be a fan of something requiring docker, but it’s often just the easiest way to deploy these types of services (and the easiest way to install it as a user).

Anyway, I’ll echo that clear, up-to-date documentation is nice. I shouldn’t have to search through actual code or the bug/issues section to find current information (but I get this is very challenging). And I’d rather projects didn’t make Discord a source of documentation (especially not the primary one).

I’ll add that having a NixOS module is a big plus for me, but I don’t expect the developers themselves to maintain this.