Ok, fair point

If I’ve understood @surewhynotlem@lemmy.world correctly, this won’t need 2 automations

When you exceed a max, I presume you’re triggering the AC to heat / cool, at this point you’d also set the “dontlogthisagain” boolean.

Then, when you’d reached the correct temp range, then you can turn off the AC and reset the “dontlogthisagain” boolean.

The conditional statements would then be “(is the temp outsode of range) AND (dontlogthisagain=True)”

You’d need to check the logic is the right way around there, but - in my head - thst should work.

Edit: actually, thinking anout this some more, you might not need the boolean, you could use the on/off state of the AC unit itself

Ahhh, well spotted

Ah, ok.

Yep, I’m in a similar situation… I have a few VMs, but not enough for lots of failover infrastructure… (redundant switches, etc)

I was thinking you might be just cloning 1 device to the other or something.

It’s now running as a VM in ProxMox on a pair of Lenovo M710q mini PCs

So, have you got High Availability setup? If so, I’d like to know more about that part…

Yeah, this is what I’d like clarified too

Am I just setting up a schedule on the server and then pushing out config to the other devices and can then shut down the server? (For example)

Where do I need to install restic?

Is this local only or to an offsite (Hetzner) location?

Let me know which repo this update appears in.

I had a quick look at the docs… so, can I backup my DB version X and restore it to DB version Y?

Ok, yeah, late to the discussion, but that’s because I used RFC2549

It’s difficult to do security-only updates when the fix is contained within a package update.

Even Microsoft’s security updates are a mix with secuirity updates containing feature changes and vice versa.

I usually do an update on 1 random device / VM and if that was ok (inc. watching for any .pacnew files) and then kick Ansible into action for the rest.

And, even further: a rust implementation vulnerability too?

(Waits for C vs Rust war to start…)

I split my loads (gigity) between the power hungry NAS and a passively cooled low power Proxmox host.

For me, most 24/7 activities are low CPU - like Home Assistant, so it needs to be there, but it doesn’t need to do anything.

Other VMs are ansible, uptime kuma, smokeping, etc… the most they use is RAM

Then the (relatively) more power hungry NAS powers up 3 times a day to syncthing everything, maybe upload a backup, and if no-one’s using Immich, etc. then it’ll power back off again.

The only other thing I have yet to downsize is my pfSense box (still a low powered device, but has fans…) and a Raspberry Pi I use for my Zigbee network.

My NAS powers up & down about 3 times a day. Drives are all fine & healthy and some have been in there for years.

I don’t disagree with your core point though…

If the drive just finished spinning down and then it’s triggered for a 1 byte file, spins down, repeat… yeah, that definitely needs sorting out.

Just the initial spin-up lag would do my head in.

But off & on ~ daily, yeah not a problem.

Not really.

Depending on how you install things, the package maintainers usually deal with this, so your next apt update / pacman -Syuv or … whatever Fedora does… would capture it.

If you’ve installed this as a container… dunno… whatever the container update process is (I don’t use them)

Ok, thanks for the insight.

I haven’t used SweetHome3D for ages and didn’t know it could use Sketchup models, so thanks for that too!

Just amazing. Thanks for sharing.

Just to give me an idea of realism… how long did this take to do? All day? Week? Month? Year?

I have played around with SweetHome3D and Gimp, but this looks like it’ll be a step higher…

Layers

HA has it’s own built in IP ban function with the HTTP(S) Integration, but that might only see NAT’d addresses (ie the entire internet has the same address as far as HA is concerned), and is really only intended for protection from someone already on your network.

You should also have some other form of external facing brute-force protection with HAproxy, nginx, fail2ban, etc.

You should have a firewall somewhere, maybe a function on your router, maybe a separate box. If possible also use geographical IP ranges to only allow your region(s).

All of that can either be at home, or on a VPS if you wanted to bounce all your traffic via a fixed location, perhaps with an outbound VPN from your home to the VPS.

Also use other network presence detection (ie ICMP ping, GPS, etc) to determine if you’re at home.

Or… as others mention… support the devs with their solution.

I setup a standard Arch install, added BTRFS, NFS, SMB, restic (for offsite backups), etc and haven’t looked back.

I installed Cockpit thinking we’d need a GUI, but syncthing just works to mirror our laptops & phones with the NAS, and with multiple versions (by syncthing) I’m happy so far

The only thing that I had issues with was Immich and (major) postgresql updates, but that’s stablising now. And, TBH, the worst thing was just having to scrap the DB and just let it rebuild it (for a few days…)

I went with BTRFS because I can “see” it with standard linux tools like gparted, clonezilla, etc. So I can backup and modify the NAS OS itself, not just my data.

Apart from updates, I haven’t touched it for years.

Or

?

Not heard of foam…

I’m not a programmer (as a day job), so I don’t use vscode, which makes me think I’d be learning to use the “wrong” tool for the job (for me), but I’ll take a look, thanks.