Also, if you get one of their units that has an ARM chip inside instead of an intel one, there is basically no chance you’re ever going to be able to use anything other than the software that they have by default.
Their x86 models are fine as you imply, just avoid ARM and you can install any OS you want.
It’s mainly Linux Unplugged where that stuff leaks into it. I haven’t heard it on “self hosted” very much.
Calibre is used as a server all the time, see calibre-web.
calibre-web is technically not Calibre and is written and maintained by different people, although it does use the Calibre database (and I believe it must be created with desktop Calibre initially). But it’s a good option and I highly recommend it.
you just load your books from Calibre (or right through USB if you’re hardcore for some reason) and you’re basically off to the races.
There’s also an OPDS server option with calibre-web that you can use to load books from if you’re using koreader.
You can also use the Kobo server replacement option with calibre-web although I personally couldn’t get it to work at the time I tried it. But this will give you a sync option that works like the official Kobo server which is quite nice.
You can also set --accept-dns to false with the commandline client although magic DNS etc won’t work.
The present for the US yeah, but much of the Western world have been following the US trend in many ways. I suspect (and hope) that it will turn back in the opposite direction as the world is flooded with cheap EVs and the public transportation work continues, as long as the rest of the world doesn’t follow the US into the abyss.
I’m expecting a relative near future where Americans are buying ever larger gas pickup trucks for 100K on credit while the rest of the world are buying small EVs for <20K, and switching to alternative forms of transport. And the Americans will swear up and down that their way is the way of “freedom”.
AMDGPU virtio native context is somewhat of an equivalent to the other options, although the pieces are not all available yet. Linux guest only as well.
And there’s Venus but that’s for Vulkan only (but a lot can be done with that alone on Linux guests).
Mailrise combined with an apprise notifier of your choice (I use gotify).
The other thing is that my libraries are alphabetical in Jellyfin, so “Anime” comes before “Kaiju”, and I truly can’t stand the idea that Godzilla gets sent to the back of the bus.
If you mean the order the libraries are listed in the web interface, you change that from “User settings” -> “Home”.
Plex is closed source and gradually being enshittified. You might not leave today, but you should have an exit plan.
btrbk works that way essentially. Takes read-only snapshots on a schedule, and uses btrfs send/receive to create backups.
There’s also snapraid-btrfs which uses snapshots to help minimise write hole issues with snapraid, by creating parity data from snapshots, rather than the raw filesystem.
True, although it’s nice to have a web UI. And I haven’t tried it myself but there’s Forgejo actions which seems useful if you need it.
Traditional server-based self-hosting will have lower average uptime, will be easier to attack, and will have a much higher chance of disappearing out of nowhere (bus factor event, or for any other reason).
It’s not a single point of failure at least but if your particular project is targeted then yeah. I was thinking more about using it for private repos, where it isn’t public at all but that’s a separate case.
This is a good argument for self-hosting Forgejo (which is quite simple compared to gitlab from what I hear).
But good to see they are standing up to this shit.
The official Forgejo instance, to be clear (Codeberg are the organisation that forked Gitea and created Forgejo).
Could be useful for web articles and scientific papers too (if it could be configured to ignore reading out all of the boiler plate and citations).
There’s likely a firewall on the system that hosts the docker services, and docker’s default bridge rules bypass it when publishing a port. And since the docker rules are prioritised, it can be quite difficult to override them in a reliable way. I personally wish that the default rules would just open a rule to the host, but there might be some complexity that I’m missing that makes that challenging.
I personally use host networking to avoid the whole mess, but be aware you’ll have to change the internal ports for a bunch of services most likely, and that’s not always well-documented. And using the container name as the host name won’t work when referencing other containers, you’ll have to use e.g. localhost:<port number> even inside the network.
You can do the bind to localhost thing that others have mentioned, as long as the reverse proxy itself is inside the docker network (likely there are workarounds if not).
The older versions will still stick around for many years; it just means apps specifically targeting GTK5 won’t support X11.
In any case, X11 has all but been abandoned already so the writing is on the wall.
It’s just saying it’s not supported, not that it doesn’t work. Depending on your country, I doubt that warranty voiding claim is enforceable either.