Yep, I do that on Debian hosts, EL (RHEL/Rocky/etc.) have a similar feature.
However, you need to keep an eye for updates that require a reboot. I use my own Nagios agent that (among other things) sends me warnings when hosts require a reboot (both apt/dnf make this easy to check).
I wouldn’t care about last online/reboots; I just do some basic monitoring to get an alert if a host is down. Spontaneous reboots would be a sign of an underlying issue.
Remember that Google News has RSS feeds! They are very well hidden, but they are there.
However, they are also a bit bad.
I started https://github.com/las-noticias/news-rss to postprocess a bit Google News RSS feeds and also play with categorization. I found spaCy worked well to find “topics”, but unfortunately I lost steam.
I think Cloudflare Tunnels will require a different setup on k8s than on regular Linux hosts, but it’s such a popular service among self-hosters that I have little doubt that you’ll find a workable process.
(And likely you could cheat, and set up a small Linux VM to “bridge” k8s and Cloudflare Tunnels.)
Kubernetes is different, but it’s learnable. In my opinion, K8S only comes into its own in a few scenarios:
Really elastic workloads. If you have stuff that scales horizontally (uncommon), you really can tell Amazon to give you more Kubernetes nodes when load grows, and destroy the nodes when load goes down. But this is not really applicable for self hosting, IMHO.
Really clustered software. Setting up say a PostgreSQL cluster is a ton of work. But people create K8S operators that you feed a declarative configuration (I want so many replicas, I want backups at this rate, etc.) and that work out everything for you… in a way that works in all K8S implementations! This is also very cool, but I suspect that there’s not a lot of this in self-hosting.
Building SaaS platforms, etc. This is something that might be more reasonable to do in a self-hosting situation.
Like the person you’re replying to, I also run Talos (as a VM in Proxmox). It’s pretty cool. But in the end, I only run there 4 apps I’ve written myself, so using K8S as a kind of SaaS… and another application, https://github.com/avaraline/incarnator, which is basically distributed as container images and I was too lazy to deploy in a more conventional way.
I also do this for learning. Although I’m not a fan of how Docker Compose is becoming dominant in the self-hosting space, I have to admit it makes more sense than K8S for self-hosting. But K8S is cool and might get you a cool job, so by all means play with it- maybe you’ll have fun!
I haven’t tested this, but I would expect there to be ways to do it, esp for VMs if they are not LXC containers.
(I try to automate provisioning as much as possible, so I don’t do this kind of stuff often.)
The Incus forum is not huge, but it’s friendly, and the authors are quite active.
Came in here to mention Incus if no one had.
I love it. I have three “home production” servers running Proxmox, but mostly because Proxmox is one of very few LTS/comercially-supported ways to run Linux in a supported way with root (and everything else on ZFS). And while its web UI is still a bit clunky in places, it comes in handy some times.
However, Incus automation is just… superior. incus launch --vm images:debian/13 foo, wait a few seconds then incus exec foo -- bash and I’m root on a console of a ready-to-go Debian VM. Without --vm, it’s a lightweight LXC container. And Ansible supports running commands through incus exec, so you can provision stuff WITHOUT BOTHERING TO SET UP ANYTHING.
AND, it works remotely without fuss, so I can set up an Incus remote on a beefy server and spawn VMs nearly transparently. + incus file pull|push to transfer files.
I’m kinda pondering scripting removal of the Proxmox bits from a Proxmox install, so that I just keep their ZFS support and run Incus on top.
If you speak Spanish, a month ago or so I was pointed at https://foro.autoalojado.es/, might be interesting to discuss the in-person stuff, although it doesn’t seem like it’s reaching a critical mass of activity :(
When I learned Git I think there were not decent tools, so I got used to the command line.
I occasionally use gitk for reviewing my commits- it’s nicer to see the files modified and be able to jump back and forth, although I get I could use git log -p instead.
I’m an Emacs user, but I don’t use magit (!)
I like some of the graphical tools- some colleagues use Fork and I like it… but as I’ve already learned the CLI, I don’t see the point for me.
I could use learning some jj because it automates some of the most tedious parts of my workflow, but I’m getting too old.
Incus has a great selection of images that are ready to go, plus gives scripted access to VMs (and LXC containers) very easily; after incus launch to create a VM, incus exec can immediately run commands as root for provisioning.
Nextcloud is in EPEL 10. You’ll get updates along with the rest of the OS.
I have been using EPEL 9 Nextcloud for a good while and it’s been a smooth experience.
If you want specifically Docker, I would not choose an EL10 distro, really. I have been test driving AlmaLinux 10 and it’s pretty nice, but I would look elsewhere.
IMHO, it really depends on the specific services you want to run. I guess you are most familiar with Docker and everything that you want to run has a first-class-citizen Docker container for it. It also depends on whether the services you want to run are suitable for Internet exposure or not (and how comfortable you are with the convenience tradeoff).
LXC is very different. Although you can run Docker nested within LXC, you gotta be careful because IIRC, there are setups that used to not work so well (maybe it works better now, but Docker nested within LXC on a ZFS file system used to be a problem).
I like that Proxmox + LXC + ZFS means that it’s all ZFS file systems, which gives you a ton of flexibility; if you have VMs and volumes, you need to assign sizes to them, resize if needed, etc.; with ZFS file systems you can set quotas, but changing them is much less fuss. But that would likely require much more effort for you. This is what I use, but I think it’s not for everyone.
I don’t use Nextcloud calendars or address books. But I assume they are included in regular backups.
I pay about 50€ for all absolute overkill Hetzner dedicated server (128gb of RAM).
I live in two different flats in different cities because of personal circumstances.
I switched to Emacs over two years ago because I was getting too comfortable in VS Code. If VS Code didn’t have the “dodgy” stuff, I would recommend it to everyone without reservation.
Emacs has been a pleasant surprise. The latest versions have introduced Eglot (LSP), EditorConfig and a few other odds and ends that make it very close to being usable with very little configuration. My latest suggestion for getting started is JUST two lines of config, and I think you can scale easily.
I just wish Emacs had started from the outset with more common keybindings- it makes it hard to recommend because you need to make a significant investment. I think it’s worthwhile, but still…
However, due to how it’s evolving lately, I suspect it might become even easier to get started with time. If they rolled in to base Emacs automatic LSP installation, that would be huge, for instance.
I assume you basically want protection against disasters, but not high uptime.
(E.g. you likely can live with a week of unavailability if after a week you can recover the data.)
The key is about proper backups. For example, my Nextcloud server is running in a datacenter. Every night I replicate the data to a computer running at home. Every week I run a backup to a USB drive that I keep in a third location. Every month I run a backup to a USB drive on the computer I mentioned at home.
So I could lose two locations and still have my data.
There is much written about backup strategies, for example https://en.wikipedia.org/wiki/3-2-1_backup_rule … Just start with your configuration, think what can go wrong and what would happen, and add redundancy until you are OK with the risks.
What volume of data you are discussing? How many physical nodes? Can you give a complete usage example of what you want to achieve?
In general, there’s a steep change in making things distributed properly, and distributed systems are often designed for big and complex situations, so they “can afford” being big and complex too.
Running LanguageTool locally is a bit of a pain, with some manual steps. Plus you have to fetch some data files. You can find around a few projects like this one to make it easier to run LanguageTool.
And yes, as the poster mentioned, LanguageTool keeps some code exclusive to their paid version. There’s a bit of a tension because they ask people not to extend OSS LanguageTool with their paid features.
There’s also this interesting clone, but it seems abandoned.
You need two drives for the OS, four for data. Hetzner boxes are cheap with 2 drives, cost multiplies if you add any other.
I see some CPU and memory usage on my setup… but I don’t even see any IO!
Literally, the IO chart for “week (maximum)” on Proxmox for my Nextcloud LXC container is 0, except for two bursts, of 3 hours of less each. (Maybe package updates?)
The PostgreSQL LXC container has some more activity (but not much), but that’s backing Nextcloud and four other applications (one being Miniflux, which has much more data churn).
Huh, what?
I see in your link that that image has support for KasmVNC, which is great and you could use to make Emacs work…
But the whole point of VS Code is that it can run in a browser and not use a remote desktop solution- which is always going to be a worse experience than a locally-rendered UI.
I kinda expect someone to package Emacs with a JS terminal, or with a browser-friendly frontend, but I’m always very surprised that this does not exist. (It would be pretty cool to have a Git forge that can spawn an Emacs with my configuration on a browser to edit a repository.)
Eh, my Nextcloud LXC container idles at less than 4.5% CPU usage (“max over the week” from Proxmox). I use PostgreSQL as the backend on a separate LXC container that has some peaks of 9% CPU usage, but is normally at 5% too.
I only have two users, though. But both containers have barely IO activity.
And also, you learn to make programs of a given difficulty by making programs of a smaller difficulty first.