I course the middle option for things I’m not hosting, but could see myself hosting in the future.

The worst part about quadlets, IMO, is that they don’t use the same key words as podman run does. So turning a working podman container into a quadlet can be challenging.

Check out Tailscale. It uses Wireguard under the hood, but it’s magic.

containers should be immutable and not be able to write to their internal filesystem

This doesn’t jive with my understanding. Containers cannot write to the image. The image is immutable. However, a running container can write to its filesystem, but those changes are ephemeral, and will disappear if the container stops.

So, slightly tangential, but I have a failed home automation project this past week.

I have been using an unofficial integration for my mini-splits for a few years. The guy who wrote it likes to disappear for 6 months at a time and it seems like it may be abandoned. It finally stopped working after a home assistant update.

I had bought some ESP based replacement dongles about a year ago and decided to finally use them. Well, not all of the features worked, so I set about writing my own firmware.

That ended up working even less well. I wasted a lot of time and effort trying to get my firmware to work before giving up and just moving to the fork of the original Home Assistant integration for the official dongles.

I hate being beholden to third party stuff like this because I have robust automation setup for my mini-splits and updates can completely break them and be a massive pain to fix.

I’m not sad I tried and failed so much as I’m just sad it didn’t work. I may try again sometime in the future.

No reason you can’t use NixOS in a VM on Proxmox.

My container host OS is another immutable, uCore, which I run in a VM on Proxmox.

I did this recently. Opendrive is free up to 5 gb and works with rclone. All I’m backing up is the config and data needed to recreate my containerized services. I’ve even had to recreate them from the backup, once.

The N100 is such a little powerhouse and I’m sad they haven’t managed to produce anything better. All of the “upgrades” are either just not enough of an upgrade for the money, it just more power hungry.

That looks very similar to ntfy. I googled “gotify vs ntfy” and found this thread on reddit (ew, I know) https://www.reddit.com/r/selfhosted/comments/shw73e/difference_between_ntfy_and_gotify/

Con: User separation. A user can create “apps” (channels), and will receive messages posted there. Users will not receive messages posted to apps they didn’t create. I haven’t yet found a way to create shared apps, or allow multiple clients to receive notifications for a given message, and I don’t want to share client logins.

Now, this thread is 3 years old, so I don’t know if this is still the case, but this is a deal breaker for me. Several of the topic I have for ntfy are also subscribed by my wife, meaning we both get the notifications. I could just post the same message to two different topics, but that would be lame.

Ntfy, if setup correctly, uses a web socket connection, which reduces the battery usage. I don’t think I ever had it setup without that, so I can’t say how bad it is. But with it, it’s not a drain for me on a Pixel 7.

I thought I replied to this earlier, but it seems like it didn’t take.

Pushover seems nice, but doesn’t seem to be self-hostable. It looks like there is a replacement service in the works called Overpush.

All I can say is that I don’t own any Apple products and never even looked at that section of their documentation. The Android and web clients work flawlessly, except that the Android client doesn’t support markdown.

I use https://ntfy.sh/ for a lot of stuff and I don’t see anyone talk about it. I recently wrote a container to poll RSS feeds and send push notifications via ntfy https://github.com/chunkystyles/rssToNtfy

I have an N100 mini PC running all of my self hosted stuff and it is amazing.

I bought an N100 mini PC (not POE) as my new server a couple months ago. I really like it. That processor is great for power efficiency.

My x86 Proxmox consumes about 0.3 kwh a day at around 15% average load. I’ve only had the Kill A Watt on it for a day, so I don’t know how accurate that is, but it shouldn’t be too far off.

To your point, I clicked on this post hoping to see what OP was going to use and why because I would like to build my own NAS some day. But like you said, this post is a waste of everyone’s time.

Learning how to use other Docker images to run Docker containers is an important first step in that process.

I’m a programmer. My foray into learning how to containerize applications started by learning how to run containerized applications. Honestly, running them is the more complicated part (for many cases, some are dead simple).

Turning an app into an image is sometimes just a simple two line Dockerfile.

I started learning with Home Assistant and the branched out to pi hole, Frigate, Mosquito, and other home automation tools. I used that knowledge to containerize a home automation tool I wrote myself.

And now I’m working on containerizing dozens of applications at work.

I’ve never done it, but it’s something I’ve seen people do to the heat spreader on the CPU. And yes it would just be mechanical sanding and polishing with paper and paste.

The aluminum has a rough looking finish. You could try giving it a mirror polish. Have you tried changing the thermal paste?

The hardware isn’t super important if you can get a Google Coral TPU. You can run Frigate on a Raspberry Pi that way. Without the TPU, it can be fairly CPU intensive.

I run Frigate on an old laptop and before the TPU it would run really hot. After it runs much cooler.