@flashfox @jakehamilton Hey, creator of nixidy here :) I'm using the generated options from kubenix still. If they don't update from 1.30 soon I might pull that code into nixidy.
My project is very much alive though :)
@flashfox @jakehamilton Hey, creator of nixidy here :) I'm using the generated options from kubenix still. If they don't update from 1.30 soon I might pull that code into nixidy.
My project is very much alive though :)
@mahmoudajawad Awesome! I hope you'll find it useful!
I have my cluster gitops repository public to show how I use it: https://github.com/arnarg/cluster
#GitOps for #Kubernetes With Nixidy and #ArgoCD
Someone wrote about my project nixidy!
https://tech.aufomm.com/gitops-for-kubernetes-with-nixidy-and-argocd/
@phileas Works!
@neo @nobodyinperson It's fairly common for companies to make a rainbow branding over pride month. Some marketing people are involved and not the entire company's/project's priorities are shifted.
My new favorite thing is to have Gemini write an architectural overview (that I'm too lazy to write) by feeding it the entire source code! With a huge disclaimer of course.
https://arnarg.github.io/nixidy/developer_guide/architecture/
@nobodyinperson I'm assuming you're using `nixosOptionsDoc`, maybe you can filter the options attribute set first like I did in nixidy: https://github.com/arnarg/nixidy/blob/main/docs/build-options-doc.nix#L63
@stphrolland @nebucatnetzer @justinas you're referencing a file outside of the git project root and it might therefore produce a different result if cloned and built on another machine, i.e. It's impure.
@musicmatze I can't really speak of the social contract of using it outside of nixpkgs but AFAIK it just excludes it from option docs.
@jakehamilton Interesting! I got a similar one the other day and thought it sounded weird af! A bit less AI though..