Here they are: https://codeberg.org/towonel/towonel/releases

I’m sorry, I’m not that familiar with LXC.

Erwan will make binaries available ASAP, would that help you?

Well, at least when someone says TiB, you don’t need to wonder if they actually mean something that is 10% more or not. Because quite often, TB (Terabyte) is written/said when the actual measurement was in TiB (Tebibyte)

Haha don’t worry, Erwan is already thinking about high availability and edge nodes closer to clients!

Maybe a Cloudflare competitor like Bunny CDN could use this to build their own tunnel service?

Very similar.

The main differences are that those projects are highly configurable and can do a lot of things, while towonel is simpler: opinionated/streamlined for use as a shared Cloudflare tunnel alternative. I also think towonel may be the only one to use QUIC for the tunnel, just like Cloudflare.

Besides that, towonel is very new and still in alpha. Rathole does not seem to be actively developed anymore, which can be a good or bad thing.

I know, the naming isn’t ideal.

On the bright side, you can now expose multiple tuwunel instances via a single towonel and federate with other tuwunels on other towonels for maximum uwu owo

Which is almost what my friends and I are doing, except we’re running continuwuity instead of tuwunel.

Thank you! I really recommend looking at RK3588 chips when upgrading from Raspberries, it’s a very capable chip with good mainline kernel support!

I recommend Talos even more though!

Renovate + GitOps. Check out https://github.com/onedr0p/cluster-template

If you don’t like Kubernetes, you can get a similar setup with doco-CD. Only limitation is that dococd can’t update itself, but you can use SOPS and Renovate all the same for the other services.

Impressive!

I don’t believe you, but I’d like to be proven wrong.

I expect you have a UPS that feeds your hosts and networking equipment and something like ZFS for disk redundancy. This protects against the most common failures and is usually enough, but there are still single points of failure in such a setup, that are not as common, not as hard to deal with through manual intervention, and quite difficult to protect with redundancy.

I would be surprised if you are protected against the following single points of failure without manual intervention:

• NAS machine (not just disk) failure. You would need to have a multi-node distributed storage, like Ceph, to protect against this.
• Networking equipment failure. I think you can do some magic with BGP to do this, but I’m not a network engineer and I’ve never set up a redundant network.

Bitnami Helm charts are not maintained anymore. There are no updates for the charts and images in the legacy repository. Try to find a different chart for harbor registry and any other bitnami images and charts you use ASAP