daqnz

> A gas-based design seems like it would be better at a small scale

The major advantage over pumped hydro would be you do not need very specific geography to make it happen (90 - 300+m change in elevation)

Completely disagree, for many people it was the only track in iTunes. And when things triggered iTunes to play it played that.

I was in an older man’s car last year. It started playing the album. He remarked “oh that always plays, I don’t know why” as I reached for the volume.

A decade later that album is still annoying people. Bluetooth triggered play or something like that and the only music on the old iPhone started playing.

> No it does not enforce ZFS or any other filesystem. That's up to you. ZFS or BTRFS are fine when indicated - and you need to know your stuff.

You are correct, it is optional and I should have made that clear. While optional it does have native support for ZFS and takes advantage of ZFS features, like instant snapshotting of LCX containers.

The turbo button actually was used to underclock the CPU's speed, not increase it.

https://en.wikipedia.org/wiki/Turbo_button

There is no OPNSense script I think historically in part because any misconfig could expose the Promox instance to the world. It is easy enough for advanced users to spin up a VM with the ISO. There has been a request for a OPNSense script made recently.

I agree with OMV. It certainly can be used as is, but not usually how people want to use it. A note was added to the script a few days ago.

> I don't see any glue scripts to get VMs talking to each other

There is a Tailscale script which technically helps them talk to each other (over Tailscale) :)

The scripts are designed to setup self contained LCX containers. We are trying to avoid building our own k8s.

> Oh wow, this is truely sad news.

Incredibly sad. It’s a real testament to tteck that he took the time to transition the project, and make his wishes known how he wanted us to proceed. Tteck is a legend.

> Still, the originating reason of this post is due to a large number of useful scripts to help make things more manageable and maintainable

Also makes it very quick to try out an application, arguably less time than even docker.

Any reason you didn't go NixOS in a Proxmox VM? The advantage would not be having to do a full reinstall if anything went wrong and being able to spin up other OS' if needed. The downside would be a few percentage of performance loss.

It is also worth mentioning that Proxmox uses ZFS making snapshotting quick and Proxmox also has a very good backup system.

If you want to treat your self-hosted applications as "sheep" (1) , then terraform k8s etc. is a better bet.

But if you are happy to manually restore from a backup or snapshot when something goes wrong, or automatically have your LXC container shifted to different hardware if you have a cluster, then Proxmox is for you. The reality is that in a home setup you will spend about as much or less time maintaining your "pets" than than you would your "farm".

(1) I write this from New Zealand

The scripts for both these projects work very well. I would recommend Home Assistant HAOS in a VM over a LXC or docker.

Along with the submitter, I am also on the team of maintainers who volunteered to help with maintenance of this project after tteck's sad news that they were entering hospice (1). The team members are all motivated individuals, who are enthusiastic on carrying on tteck's legacy.

We are moving forward in a transparent manner and I am more than happy to answer any questions.

(1) https://news.ycombinator.com/item?id=42016605