In term of software compatibility, on Linux, you have the option of making chroots. Since the kernel devs makes a lot of effort to preserve compatibility, old software can still work fine. If I remember correctly, some kernel devs tested a while ago some really really old versions of bash, gcc, etc, and they still work fine with modern kernels.
Red Hat. Probably Canonical too.
I know it for a fact since I worked for a bank that chose Red Hat and since I also know someone working for Red Hat.
For those wondering, it also works with a Linux VM:
- Host: AMD Ryzen 9 3900X + Proxmox
- PCI passthrough for an Nvidia RTX 3060 12GB
- A Debian VM with 16GB and as many cores as the host have (if you set less cores, you will have to tune cpu affinity/pinning)
- An HDMI dummy
- I stream the VM to my office using Sunshine and Moonlight
It's not easy to set up, but it works. I'm able to run some games like Borderlands 3 running at ~50FPS with a resolution of 1920x1080 with visual effects set to the max (important: disable vsync in the games !).
Only problem is disk access. It tends to add some latency. So with games coded with their ass (ex: Raft), the framerate drops a lot (Raft goes down to 20FPS sometimes).
Yes I would count this game as self-hosted (as long as you don't need a third-party service to start it). And yes I agree it is a pretty wide definition. But at the same time, I really think there are a lot of good reasons to not dismiss it:
- I think it is the simplest form of self-hosting you can do and it is doable by anybody without much technical expertise. For people with little to no technical expertise, it's the perfect gateway to self-hosting. All you need to start is a backup drive.
- For a single person, it's actually the approach that often makes the more sense.
- And even for technical people, sometimes you just don't want to deploy and maintain yet-another-service.
- And finally, you can still access your data when you're offline.
To be honest, when it comes to self-hosting, I can't shake this feeling that a lot of people are dismissing desktop apps immediately just because they are not cool nor hype anymore.
Regarding Syncthing, if I'm not mistaken, the Web UI can be opened to the network (most likely for headless servers) but by default it is only reachable through the loopback.
Regarding OP, for me, it wasn't entirely clear at first whether they wanted network access or not. They clarified it later in comments.
It is "hosted" on your workstation. There is no need for a server-client relationship for self-hosting.
By requiring a server-client relationship, you're making self-hosting uselessly hard to deploy and enforce a very specific design when others (P2P, file sync, etc) can solve the same problems more efficiently. For example, in my specific case, with Paperwork + Nextcloud file sync, my documents are distributed on all my workstations and always available even if offline. Another example is Syncthing which IMO fits the bill for self-hosting, but doesn't fit your definition of self-hosted.
No it does not.
Self-hosted implies self-hosted. AFAIK, the end goal is being as autonomous as possible technologically-speaking. Why exclude desktop applications ?
AFAIK, unfortunately Dia hasn't been maintained and hasn't got a new release for a really long time. It's still using GTK2.
You don't even need Docker for draw.io: https://github.com/jgraph/drawio-desktop/releases
You can use du -sh to figure out what's using most of the space. Something along the line of:
sudo -i
du -sh /home /usr /var
du -sh /var/*
du -sh /var/log/*
# etc
If it's one of your log files (likely), you can run something like tail -n 100 /var/log/[culprit] or tail -F /var/log/[culprit] to see what is being flooded in this log file exactly. Then you can try to fix it.
As suggested by others, your processes may be using too much memory. However I would also suggest you keep an eye on the output of dmesg. Maybe one of your disks is failing.
Oh actually if you are worried about vendor lock-in: Meshcentral is opensource. So even if they decide to try something stupid, a fork would be likely to happen.
I think there is some confusion here.
Paperwork is a desktop application, not a web application. (eh, self-hosting doesn't necessarily always imply web applications ! :). I for one use Nextcloud and nextcloud-desktop to keep my Paperwork work directories in sync on all my computers.
Paperless is a web application. Paperwork is a desktop application.
I self-host Meshcentral. I haven't seen any limitation at all. I don't know if there are limitations when you use meshcentral.com instead of self-hosting.
Paperwork seems to fit most of the bill except for one thing: it won't scroll to where the search hit is (but it will highlight the matching keywords).
Just beware Paperwork won't just create an index. It'll organize the PDF its own way in its own work directory.
(full disclosure: I'm its main dev)
Based on my tests on my family and friends, the main problem is tech support. Most geeks seem to assume other people want the same things than themselves (privacy, freedom, etc). Well, they don't. They want a computer that just works.
Overall when using Linux, people actually don't need much tech support, but they need it. My father put it really well by saying: "the best OS is the one of your neighbor."
I apply few rules:
-
The deal with my family and friends is simple: you want tech support from me ? ok, then I'm going to pick your computer (usually old Lenovo Thinkpads bought on Ebay at ~300€) and I'm going to install Linux on it.
-
I'm not shy. I ask them if they want me to have remote access to their computer. If they accept, I install a Meshcentral agent. Thing is, on other OS, they are already spied on by Google, Microsoft, Apple, etc. And most people think "they have nothing to hide". Therefore why should they worry more about a family member or a friend than some unknown big company ? Fun fact, I've been really surprised by how easily people do accept that I keep a remote access on their computer: even people that are not family ! Pretty much everybody has gladly agreed up to now. (and God knows I've been really clear that I can access their computer whenever I want).
-
I install the system for them and I make the major updates for them. Therefore, if I have remote access to the system, I pick the distribution I'm the most at ease with (Debian). They just don't care what actually runs on their computers.
-
When they have a problem, they call me after 8pm. With remote access, most problems are solved in a matter of minutes. Usually, they call me a few times the first days, and then I never hear from them anymore until the next major update.
So far, everybody seems really happy with this deal. And for those wondering, I can see in Meshcentral they really do use those computers :-P
Also thanks to Wine/Proton. You have to give it to Valve : it works surprisingly well.
At first sight, it looks like it can be used with chroots thanks to systemd-nspawn (I haven't tried it though)
