Spyke

Replies

linux

Comment on

Sync bash aliases and ssh keys across devices

I'm surprised no one mentioned ansible yet. It's meant for this (and more).

By ssh keys I assume you're talking about authorized_keys, not private keys. I agree with other posters that private keys should not be synced, just generate new ones and add them to the relevant servers authorized_keys with ansible.

Comment on

Swiss Hospital Association director says single health insurance is ‘worth considering’

Reply in thread

Insurance is privatized with many providers, however the 'base insurance' covers the same at all providers and is mandatory to have for all residents. However base insurance prices still vary between providers every year, so people are encouraged to switch the provider regularily, which is a business on its own with brokers / call centers getting bonuses for every 'sign up', which means a lot of wasted money:

https://www.emolument.com/salary-reports/jobs/insurance-broker/45892

Comment on

A dozen or two TB of storage for media on the cheap?

Reply in thread

If this fits your budget (you still need the actuals disks..) it's not a bad choice. Speed should be sufficient for HDDs, as it's USB 3.

As the other poster suggested, don't use its hardware raid. Use it as a JBOD and configure the raid in Linux with ZFS or similar.

And never forget: RAID is not a backup! You still need to do regular backups, at least for important data.

Comment on

Uptime-kuma & Docker: Timeouts when monitoring services on same host

Reply in thread

It matters only if "the docker hosts external IP" your dns resolves is a public IP. In that case packets travel to the router which needs to map/send them back to the docker hosts LAN IP (NAT-Reflection). With cgnat this would need to be enabled on the carrier side, where you set up the port forwarding. If that's not possible, split-DNS may be an alternative.

If "the docker hosts external IP" is actually your docker hosts LAN IP, all of that is irrelevant. Split-DNS would accomplish that.

linux

Comment on

What's an elegant way of automatically backing up the contents of a large drive to multiple smaller drives that add up to the capacity of the large drive?

I ran into the same problem some months ago when my cloud backups stopped being financially viable and I decided to recycle my old drives. For offline backups mergerfs will not work as far as I understand. Creating tar archives of 130TB+ also doesnt sound like a good option. Some of the tape backup solutions looked to be possible options, but are often complex and use special archive formats...

I ended up writing my own solution in python using json state files. It's complete enough to run the backup, but otherwise very work-in-progress with no restore at all. So I do not want to publish it.

If you find a suitable solution I am also very interested 😅