ominous ocelot

I would get some cheap maybe even used X86 hardware to start with. Depending on your backup needs, you might need more than one M2 or SATA port. If you plan to use it as an always on device, I would keep the power consumption in mind. A celeron N could be the way. The cpu processing power is, in my experience, not the limiting factor for a self-hosted environment. Give it lots of RAM, every virtual machine and every running service needs space.

Using arm, like a Raspberry Pi, is not bad if you can find all your Docker images and binaries, compiled for this platform. I went away from it.

There are many possible distributions and software you could use, it really depends on personal preference.

Can I have everything? Inside and outside the Venn circles!

It is called sampling and recombination, which is perfectly fine. The only metric should be that the final product masters the testing parkour. And that parkour better be worth its name. :)

It would be fun if they would never reach 3.15. Because of the pi joke. But semantic versioning has a say in this, too. Sadly.

You can never be sure. Regressions do happen.

First evaluate it on your test setup.
— useless hint of the day

Some fs can do snapshotting (btrfs, zfs,…). Second best would be a current backup to restore from.

rsnapshot is a script for the purpose of repeatedly creating deduplicated copies (hardlinks) for one or more directories. You can chose how many hourly, daily, weekly,… copies you’d like to keep and it removes outdated copies automatically. It wraps rsync and ssh (public key auth) which need to be configured before.

• journalctl shows the oom event
• Container limits you can limit container resource usage
• also you can look at container stats to maybe identify the culprit. Or cyclically write the stdout of ps to a file to identify the memory hungry process.

I dare you! You got version control and good unit test coverage after all, no? ;)

Now throw away the copied part.

Every decade has at least one of these buzzwords (multimedia, internet/ online, social media, mobile app, blockchain, cryptocoins, micropayment, delivery, ai,…)… They can be used to attract dumb investor’s money but they have their useful sides too.

Ok. They are just buzzwords which outline a set of tools. They are worthless without a realizable concept with a benefit for the end-user. And the use of the right tool for the job. So, I’m not sure about useful cryptocoins and blockchain use cases (I wouldn’t count financial speculation as particularly useful).

Huh. 101.

Maybe the comparable.is_greater_than(int) function needs some work. Or someone compared strings. :)

Should have been digits

Debian + LVM + Incus :)

:)

Damn.

tar - h

The h4 already can be a managed switch itself (2" 2,5gbit + 4*1gbit with the nic addon.) if you want it to be one. Linux as the host OS (VLANs, bridges) - netplan works well for me. Some VMs and containers on top (lxd, incus, some use proxmox) for router/ firewall/ vpn-gateway (opnsense, ipfire,…) and other functionality which you don’t want to run on the host OS directly. The cpu is fast enough to run all your services at once. It all comes down to RAM.

IMO there is not one right way. It all depends on what you want to achieve. Also a lot depends on, whether you want results fast or if you enjoy the tinkering while learning.

There is a version of Doom, where you can shoot at random files on your disk.

“SDD”?

Yes. Solid Disk Disk.