@caddyserver@giteaio I realized that the sponsorship dropped due to an issue with my card, so the one that just came in is to make up for the 5mos that were missed from the last re-occurring one, and when GH lets me signup for monthly again (can't mix with active one-time), we will be re-occurring.
@giteaio@scruelt Since you pinged me here, I will respond as I did in the issue. I ask you to review your behaviour towards other humans, you should not treat anyone like that. I did read the issue, and gave you information about what was going on. Everyone is welcome to re-open closed issues.
@alexellisuk Ah, thanks for linking that. I was hoping to avoid what you had in there with the intermediate step (as we are doing that already), but good to know that is the approach others are taking.
@alexellisuk@giteaio I played around with it as with the helm chart we need to install helm for testing/whatnot, and so I'll need to integrate it into the official repo to remove some bash
Inspired by @rawkode's @KubeHuddle talk, where at the end he said we should all strive to share our knowledge. I got my act together and finished a blog post in my drafts folder. Appropriately enough it is about Kubernetes, and auto-updating deployments https://t.co/HgZ8WDj4v8
In my spree of technical blog posts this month, I just wrote about publishing a static @GoHugoIO site to host on @BunnyCDN in case you wanted cheaper bandwidth than Netlify
https://t.co/WmCFtyUrmz
Channel my inner @nosceon, and wrote a blog post about using #Vault as an SSH CA. This has allowed me to not worry about putting each of my SSH pub keys on the many servers I manage, and removing them when I have to rotate keys.
https://t.co/kzWew9jnQb
We just released #Gitea 1.19.1!
There's one breaking change, which is abnormal for a minor release, we don't expect it to affect many users if any at all.
As always, please update when possible, and report any issues you have to the issue tracker ❤️
https://t.co/S0St1q94Hg
@mholt6 taking adam&gitea out of replies, as I have a Q for you.
You mentioned previously you host discourse yourself, 1. did you know they have an OSS program? 2. if yes, did the program not work out for you for whatever reason (too many views, wanted a custom domain, etcc..)? 3...