There is winapps that does the bottle thing for you in a background vm.

https://github.com/Fmstrat/winapps

Before RustDesk I have used NoMachine but that’s completely proprietary (Luxembourg company, except for the old core protocol - NX 1).
Afair I am afraid that there isn’t an all-in-one foss desktop remote software as good as RustDesk currently.

Now it looks correct:)

Big stuff

-euo pipefail now being a posix standard is really awesome, as well as readlink and realpath (didn’t even know these last two were non-standard).

Formating of the configuration content under point 4 seems to have spilled out, you might have to use a triple backtick followed by newline if it’s a multiline code/content.

Numbers from my instance, running for about a 1 year and with average ~2 MAU. According to some quick db queries there is currently 580 actively subscribed communities (it was probably a lot less before I used the subscribe bot to populate the All tab).

SELECT pg_size_pretty( pg_database_size('lemmy') ): 17 GB

Backblaze B2 (S3) reports average 22.5 GB stored. With everything capped to max 1 USD, I pay cents - no idea how backblaze does it but it’s really super cheap, except for some specific transactions done on the bucket afaik, which pictrs does not seem to do.

According to my zabbix monitoring, two months ago (I don’t keep longer stats) the DB had only about 14G of data, so with this much communities I am getting about 1.5G per month (it’s probably a bit more as I was recently prunning stuff from some dead instances).

Prometheus says whole lemmy service (I use traefik) is getting within about 5 req/s (1m average) though if I go lower it does spike a lot, up to 12 requests within a second then nothing for few.

Attach it to the VM

Is this possible only with the extra, bought storage boxes ? Or is this possible even with the free 100G backup boxes offered with each dedicated machine ? (Or is this just nfs mount?)

We have a dedicated machine in a project from Hetzner with big raided hard disks but the latency is starting creep up on us, moving some of the data off to the faster ssd/san boxes would be rather helpful.

Run your ip through ip abuse databases to make sure there is nothing wrong perceived from outside.

I’ve once tried WinBTRFS and on top of not making it work I still have leftover drivers that can’t be deleted.

I just use ntfs3 and ever since tweaking steam so that it does not put proton compatdata on it I didn’t have to reboot and run chkdsk for months now.

Uh probably not that helpful but I am somewhat sure that this was super easy to do from virt-manager (on Arch qemu & kvm, virtualizing Tiny11 )

So the lower-ish difficulty answer would be to run the iso installer in a VM with the usb stick forwarded to that VM.

Or you can learn what those fancy installers do: on debian you would use debootstrap

Here seems the whole guide on how to install debian manually with it:
https://gist.github.com/tr3buchet/6407920

Btw, this is also basically how you install Arch. As of until recently there wasn’t any installer and you had to go through each step manually (create partitions and fs, install the base system with <insert distro specific tool>, chroot, update fstab, distro specific finishing touches, voilà)

/sbin are system binaries, eg root only stuff, dunno the rest but I would guess there are some historical reasons for the bin usr/bin separation

How did you install jellyfin?

It should not core-dump (read: hard crash, something has gone terribly wrong), at best you should get a configuration error and errors like that.

You can see the logs of any systemd service/unit with this: journalctl -u <name of sevice> so in this case journalctl -u jellyfin (Tip: add -f to follow the output of a running service - useful for monitoring).

Note that some programs log to their own files (and not to stdout) so if the above command comes out empty you should look into /var/log/ directory.

Afaik RedBot (oss, extensible discord bot in Python) used it to allow people to run python scripts directly from discord without access to the file system, network and to limit the run time.

In my book I’ve had categorised it as a lower-level tool for security and sandboxing, a lot lower level then firejail is.

I would worry about getting rate-limited then, I’ve seen some content servers just be very picky about making too many requests (through jumping in the video too far too often).

You could also (hard) limit the total (virtual) memory process will use (but the system will hard kill it if tries to get more) with this:
systemd-run --user --scope -p MemoryMax=8G -p MemorySwapMax=0 prismlauncher

You would have to experiment with how much Gs you want to specify as max so that it does not get outright killed. If you remove MemorySwapMax the system will not kill the process but will start aggressively swapping the processes’ memory, so if you do have a swap it will work (an depending on how slow the disk of the swap is, start lagging).

In my case I have a small swap partition on an m2 disk (which might not be recommended?) so I didn’t notice any lagging or stutters once it overflow the max memory.
So in theory, if you are memory starved and have swap on a fast disk, you could instead use MemoryHigh flag to create a limit from where systemd will start the swapping without any of the OOM killing (or use both, Max has to be higher then High obv).

Fabric is one of many mod loaders ala Forge. It’s newer and less bulky then Forge (but afaik it already did have it’s own drama so now we also have a fork called Quilt, the same goes for Forge and NeoForge).

The mods I’ve specified above can be considered as a suite replacement for the (old) OptiFine.

E: For example this all the mod loaders modrinth (mod hosting website, curseforge alternative) currently lists:

As a side note and a little psa, if you need to squeeze out more overall performance of out of MC (and you are playing vanilla or Fabric modpack) I very much recommend using these Fabric mods: Sodium, Lithium, FerriteCore and optionally Krypton (server-only), LazyDFU, Entity Culling, ImmediatelyFast.

Big modpacks that add a lot of different blocks will also always explode the memory usage as at the start, Minecraft pre-bakes all the 3d models of the blocks.

That yor votes are already public.