@wyri unpopular opinion: Sometimes it’s just time to say goodbye.
There are just way better alternatives to #PHP for #K8s platforms. The core concept of configuration and runtime management was build for something different, out of different reasons.
„Ohne Helm und nicht angegurtet
Dazu komme, dass jedes zweite Kind im Lastenfahrrad keinen Helm trage und ein Drittel gar nicht oder nicht korrekt angegurtet sei.“
(Fragt mal so einen durchschnittlichen Niederländer, ob er nicht lieber mal mit Helm…?? Das Gelächter wird dich noch im Traum verfolgen.)
Traurig #WDR , sehr traurig.
@DieFischerinW genau den Unsinn habe ich auch gelesen. Keine Erwähnung der Infrastruktur und des Verhaltens von Autofahrern* als Unfallursache. DARAN HÄNGT ES, @aktuelle_stunde@wdraktuell &nicht an Styroporhalbkugeln!! Pünktlich zum "Saisonstart" kommt wieder diese Meldung. @vcdnrw@ADFC@SheDrivesMobility
For the past few years (basically within the first few months of using Emacs in 2020) I’ve been using #Helm. My understanding of how completing-read and the minibuffer in #emacs should work are thereby strongly influenced by this experience.
This weekend I finally had some time to play with #Vertico (and marginalia, consult, orderless… inspired by Prot's video). Probably I’m holding it wrong but it was not a smooth experience. Is it correct that vertico ignores the sorting of the collection used? Is there a way to change this? Why is the minibuffer here broken? Any advice would be welcome.
The images attached show the results for (completing-read "" orgrr-selection-list) in helm and vertico.
@sachac Thanks! This would explain why sorting is correct in Helm. It also explains why (setq vertico-sort-function nil) produces the correct order in Vertico.
This is why I love #Renovate over #Dependabot: it picked up #Docker tags somewhere deep inside some #Helm chart, plus picked up all the Helm charts in my #TerraForm that need updating. Looks like I'll be updating everything tomorrow (well today since it's past midnight) 🎉🎉🎉#
@kisharrington I don't know if Daniel Mendler is on Mastodon, but feel free to ask me any questions you have about those packages, I'm pretty familiar with his packages too. (I wrote orderless and embark, he wrote vertico and consult, and we started marginalia together though we does most of the maintenance now —mostly because he's superfast and beats me to the punch almost every time.)
Hi all, I've just migrated from @irfan to this account on sakurajima.social. I'll also be attempting to migrate my main account @irfan to this one in the coming days, but I'm expecting nothing on that front since it's failed so far.
I've moved to multiple servers throughout my time on the #Fediverse in pursuit for a "permanent" instance to be on, and I've never had the chance to write an #intro post lol so this will be my first.
I'm a 26 year old (in Nov 2024) (gfdi) programmer obsessed with languages such as #Python and #Shell, frameworks like #Django, and #CloudNative shenanigans like #Docker, #Kubernetes, and #Helm. I'm also obsessed with #FOSS and #Linux, and promoting them to be more viable each day for the masses so everyone could have not just free but secure access to daily computing.
I'll be using this account to mostly document my passions through mini reviews or rants. I have another picture-based account over on #Pixelfed, @irfan. All images I have posted and will be posting will include descriptive/alt text, including my pfp and banner. I also have some bots for posting local (to me, #Malaysia) #news and other relevant data cos the #Mastodon API is just so fun to play with.
A lot of my apps require a scheduler, I've always given the option to choose between using #APScheduler or #Celery/#Redis for that. So tempted to drop Celery though because of just HOW MUCH RESOURCES it needs to even work, and when it doesn't work it's all silent about it. In my #helm charts, I could set very low (default) resource limits because they've been tested to work/be sufficient with APScheduler and the rest of the app - because of Celery though, I'd need to set a much higher default.
I feel like I'm bombarded with things I wanna do devel-wise so I'm just gonna write them down here so I don't feel overwhelmed lol:
Work on my #Mastodon - #Djangoframework creatively named as mango to be used as a base for all of my other Masto-Django projects.
Port my other creatively named projects such as rizz (RSS-Masto bots like @lowyat and @soyacincau) and waktusolat (@waktusolat) to use mango as a base when it's finished.
New project based on mango to track/update local COVID-19 data on Mastodon.
Update my long abandoned clog (web blog/todo/money tracker app) project.
Develop a new web app, that could potentially be used as an e-invitation card/management portal. If this one goes well, I could self host/deploy it for my own wedding eventually lmao.
Create a Helm chart for #Kutt (FOSS URL shortener) and deploy it to my homelab.
Lots to do, for someone with extremely short attention span.
After long days of coding and longer nights debugging, I'm finally starting to see the light from the end of the tunnel for my mango project.
I have to say tho, despite the trouble/hassle, it was a really good decision trying to make it. Future maintenance/development of my other Masto bot projects will become (or rather, has already been made) much easier thanks to them sharing a base (mango) and making a "standard" for projects of mine that extend it to conform to. A lot of enhancements will come to rizz and waktusolat by the end of this.
Also adding to my todo list, a (local) COVID-19 data tracker on Mastodon. I already made one for Telegram during the start of the pandemic, maybe it's time I bring it to Masto.
Is there really no way to programmatically create a #Helm values.yaml with our values specified through set etc.? Seems like a pretty simple use case they could handle but I'm not seeing any docus/discussions saying how or if we could even do this.