Letting the user choose in nixpkgs
Wouldn't it be nice to choose the reverse proxy you want? Why is nginx hardcoded nearly everywhere? Where is declarative LDAP and SSO integration?
Contracts codify expectations between a consumer and a provider. If enacted at the correct level, it allows to decouple modules, increase code reuse, reduce maintainer burden, increase test coverage, interoperate with non NixOS systems, and most importantly, let the user choose an implementation for a feature.
There has been a lot of experimentation in SelfHostBlocks and a lot of efforts to integrate contracts in nixpkgs. This talk will show what nixpkgs could look like with contracts, the current state of contract integration in nixpkgs, how to contribute and where help is most needed.
I’m a software engineer advocate of Self Hosting and Data Sovereignty. I am specifically focused on how to improve long term maintainability of software and hardware. I work on SelfHostBlocks and Skarabox to lower the bar of entry to these domains.
I am also interested in distributed programming and declarative infrastructure as well as IoT electronics and smart home projects.
I am working at Wedo as a half Full Stack half DevOps Engineer. We work in Go and Typescript. I was previously working at Fastly on the Next-Gen Waf project, helping secure the web.
I’m the father of 6 wonderful children and married to a wonderful wife.
You can read my blog posts on my blog.