talkingpumpkin

joined 2 years ago
[–] talkingpumpkin@lemmy.world 1 points 3 days ago

By that reasoning, backup isn't redundancy because you'll lose your data if the backup gets corrupted while restoring.

That said, there's nothing wrong in redefining "redundant" to mean "having two or more duplicates"... you should however tell people if you do, to avoid misleading people that assume the dictionary definition.

[–] talkingpumpkin@lemmy.world 15 points 4 days ago (4 children)

RAID (except RAID0) is data redundancy, it just isn't backup (ie. it doesn't help if you accidentally delete stuff, or if some bug corrupts it, or if you drop the computer while moving it).

[–] talkingpumpkin@lemmy.world 6 points 6 days ago

is there an easier way to do self-signed certs besides spinning up your own certificate authority?

Letsencrypt works fine, just use a "real" domain and DNS challenge.

Your service will need to be on the "real" domain, but it won't need to be accessible externally and you won't need a public DNS entry for it (of course your VPS will still need to be able to resolve the backend's name).

[–] talkingpumpkin@lemmy.world 1 points 6 days ago* (last edited 5 days ago)

In layman's speech (my speech) raid 1 and mirroring are essentially the same thing.

Technically, IIUC RAID is only used for hardware raid controllers, ZFS calls their equivalent RAIDZ1 (and I think it stores data in one disk and parity in another?) and both LVM and btrfs call theirs mirroring (each with its nuances). Whichever you pick, it's a mode where you use two disks at 50% efficiency and your data survives the loss of one disk.

There are configurations that use more disks with higher efficiency than 50%, but I would avoid them in a homelab because the more disks you have, the higher the power drain and the higher the chance that at least one of them will fail. In a homelab scenario what you really want to minimize is the chance of needing to perform maintenance (replacing a drive in a RAID and restoring from a backup are both a hassle, and it's not like the first requires significantly less work).

In your shoes (and in mine, whenever I'll need to redo my RAID1 NAS), I'd skip RAID altogether and use the extra disk for extra backups of the data I care about.

Most of my NAS is filled with movies I've ripped, and I honestly wouldn't really care much if I were to lose them: the movies I may want to re-watch are really few and I can just rip them again (or even buy them again) if the need arises.

Backups are enormously more important than RAID (will RAID do anything for you if you accidentally delete your family photos? what if the NAS floods or gets dropped on the floor?): you should really direct your time/resources/effort towards setting up automatic and monitored backups before worrying about RAID.

[–] talkingpumpkin@lemmy.world 11 points 1 week ago* (last edited 1 week ago) (3 children)

A NAS is any computer with space/connectors for drives and an ethernet port... it doesn't need to be powerful or state-of-the-art, and there's really no reason it should be expensive (besides the drives).

Of course companies will be more than happy to sell you an outdated J4125-based computer with 4 disk bays for over 500EUR, but that doesn't mean you have to bite.

As for RAID, if you want to use it, just setup mirrored drives (ZFS, BTRFS or even LVM) and be done with it: you'll need backups anyway so don't overthink it. Unless you want to avoid downtime (which isn't probably a big issue for most of your data?), you can do without RAID and just restore from backup if a drive happens to break.

If you don't want to build your own PC, I've heard good things about these: https://aoostar.com/collections/nas-series (beware: I didn't try any of them - my N3150-based NAS is not old enough to need replacement yet)

[–] talkingpumpkin@lemmy.world 10 points 2 weeks ago

Leverage whatsapp and hang good old posters around the neighborhood?

[–] talkingpumpkin@lemmy.world 7 points 1 month ago

Did you ask an AI to do the list for you? (no need to answer)

[–] talkingpumpkin@lemmy.world 19 points 1 month ago

Intriguing.

What's the mechanism for dealing with spammers?

In lemmy there's a clear escalation path that will lead to either the spammer's instance dealing with the issue or the instance itself being de-federated.

How would that work in a p2p system?

Each user having to individually block every spammer will work as well as it did for email back in the day.

[–] talkingpumpkin@lemmy.world -3 points 1 month ago

Your source?

Anyway, even if that was the case, it's not like Putin cannot have opinions that also happen to be true (is water less wet if Putin thinks it's wet?).

Don't get me wrong... I'm not defending that inhuman monster, but he is definitely not an idiot.

I'd even say he might be one of the shrewdest and most cunning government heads out there, which of course only make him more dangerous.

19
submitted 3 months ago* (last edited 3 months ago) by talkingpumpkin@lemmy.world to c/europe@feddit.org
 

Delusional.

 

A lot of selfhosted containers instructions contain volume mounts like:

docker run ...
  -v /etc/timezone:/etc/timezone:ro \
  -v /etc/localtime:/etc/localtime:ro \
  ...

but all the times I tried to skip those mounts everything seemed to work perfectly.

Are those mounts only necessary in specific cases?

PS:

Bonus question: other containers instructions say to define the TZ variable. Is that only needed when one wants a container to use a different timezone than the host?

 

Prometheus-alertmanager and graphana (especially graphana!) seem a bit too involved for monitoring my homelab (prometheus itself is fine: it does collect a lot of statistics I don't care about, but it doesn't require configuration so it doesn't bother me).

Do you know of simpler alternatives?

My goals are relatively simple:

  1. get a notification when any systemd service fails
  2. get a notification if there is not much space left on a disk
  3. get a notification if one of the above can't be determined (eg. server down, config error, ...)

Seeing graphs with basic system metrics (eg. cpu/ram usage) would be nice, but it's not super-important.

I am a dev so writing a script that checks for whatever I need is way simpler than learning/writing/testing yaml configuration (in fact, I was about to write a script to send heartbeats to something like Uptime Kuma or Tianji before I thought of asking you for a nicer solution).

view more: next ›