

I’m sorry, I’m not that familiar with LXC.
Erwan will make binaries available ASAP, would that help you?


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.


For those who block Lemmy.world :
Towonel: Open Source drop-in Cloudflare Tunnel alternative
So you don’t want to port-forward on your home router or have Cloudflare decrypt all your traffic? Check out Towonel.
Most open source Cloudflare Tunnel alternatives involve setting up a VPS, terminating TLS there on a reverse proxy, then setting up a Wireguard tunnel to your server at home.
Towonel is different: it does not decrypt your traffic on the VPS and you can easily share one, so not every self-hoster has to buy and maintain a VPS.
Check it out!
Mastodon link: https://gts.erwanleboucher.dev/@eleboucher/statuses/01KS4YNA2SYMSP0FSKJVNJA155
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.


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


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.
Or LazyVim
I was just relaying how the OpenCloud people explained it to me at Froscon this year
Nice, I hadn’t heard of that one yet!
Thanks for your feedback!
Some thoughts:
cliff.toml (generated with git-cliff --init) to ignore any commits that aren’t interesting to your usersI 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.
Just like the old PHP based OwnCloud was forked to NextCloud for governance reasons, we now also have a fork of OCIS under the name OpenCloud:
Here they are: https://codeberg.org/towonel/towonel/releases