What I might consider is a “winterized” variable per hose/pipe that may be a concern, and only notify if winterized is false for those, and have the notification list specifically not winterized.

That state would be manual per, but then you would be able to get a more meaningful reminder to only those that would be at risk.

No worries!

Because it creates an OT discussion and the tag doesn’t apply. A discussion I won’t necessarily know about until after its gone on and gotten heated.

Comments aren’t for rule policing, just use the report button please.

Italics = fixed crappy autocorrect. Be a use? Wtf.

Up until the point the resources available (CPU/ram/storage) become a problem.

That said, managing those apps as installations can be troublesome, which is why people like podman/docker. Updates are more contained, system updates don’t break services, and vice-versa.

A more comprehensive option is to use Proxmox or similar to manage services as a combination of Virtual Machines, LXC’S (Linux containers), and maybe podman/docker on a VM. Note that Proxmox techincally supports importing a docker container as an LXC, but this is a one-time action. Not recommended. (EDIT: For the record, there is a Proxmox on pi effort, but its community supported not Proxmox supported as of the last time I looked.)

Navidrome and pihole are the easy ones on that list also. Jellyfin itself is easy, but you aren’t going to be transcoding video on the fly, so make sure its in a format that is friendly to all of your devices, transcoding in advance if needed.

I’d sum it up with:

“Ew.”

Its one thing to offer bespoke customization for businesses. Its entirely another to work to prevent any indication that the software is being run by someone other than the creator of the software. IMO, it goes against self hosting as a practice.

It could be everything I want and more, and it would immediately turn me away. Which, in turn, would also turn me away from recommending it to others, including businesses.

I’d call it a pretty bad strategy.

Secure enough I suppose.

f2b at the FW, auth with MFA for anything exposed, anything local only has restricted access at the FW level, with exposed (via proxy) and local-only (separate proxy) on different vlans. Each service is (typically, with some exceptions) an LXC, with additional rules and templated out based on use case. The few cases where docker is involved is local-only and that has its own vlan with additional rules.

rclone crypt

You can, but you need their app.

That isn’t something I’m going to do, so I tag manually instead.

I know, thats why I’m asking a question.

Well, perfect use case for the test immich instance!

I’ve got a few day trips recently that will make for good tests for over the weekend.

Those changes happened in less than an hour?

I’m a bit confused because your last paragraph asks direct questions that are already addressed.

The immich service connection.with writeback is awesome!

My kids have some dinky little digital cameras with no GPS or WiFi or anything, just writes photos locally to microsd, so obviously no location data. I use my phone, sure, but when traveling I’ll use my DSLR that also has no GPS (OK it does have WiFi, but I don’t use it).

Which turns into me tagging every time we get back from somewhere.

Going to give that immich link a try!

Its relatively new (past 6 weeks or so?) due to an influx of projects and a lot of repeat questions, and after some community discussions its where things landed.