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.

ASUS Linux is a community effort, not part of ASUS the company.

I’d love to be wrong, but I can’t find any sources on significant contributions from ASUS.

“My browser is slow because Venus is in Taurus now”

This joke is taken insanely far

Thank you for the feedback, could you be more specific?

Is it crossposting? Or Kubernetes-specific content in /c/programming?

Or giving tips on how to practice for specific certification exams?

Or do you dislike the prose format? Too much context? Do you prefer bullet points?

Or is it that I put an image while the link should be the focus? I see now that in my client I have to click through to the original post first to see and visit the URL

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

That is indeed a difficult problem. Integration testing and contract testing can help to avoid this, but one can never be 100% sure.

https://xkcd.com/1172/

Or LazyVim

https://lazyvim.org/

Nice, I hadn’t heard of that one yet!

Thanks for your feedback!

Some thoughts:

• You could configure your cliff.toml (generated with git-cliff --init) to ignore any commits that aren’t interesting to your users
• You could use “squash merge” to the prerelease/staging/development branch so that you can commit without worry, and then only have your PR titles follow conventional commits (if the change is interesting to your users)

I should probably add those to the blog.

But yeah, I get preferring to write manual tailored changelogs. Personally I am just a little neurotic about single source of truth and a huge Git nerd. And I know that at least in this job, my users are neurotic enough to prefer completeness.