Jetify
@jetify.bsky.social
Our team will be at Kubecon next week, talking Devbox, Nix, and Cloud Dev Environments! Let us know if you're around and would like to meet up
#Kubecon #CloudNativeFdn #OpenSource #Kubernetes #Nix #Devbox
#Kubecon #CloudNativeFdn #OpenSource #Kubernetes #Nix #Devbox
November 7, 2024 at 12:25 AM
Our team will be at Kubecon next week, talking Devbox, Nix, and Cloud Dev Environments! Let us know if you're around and would like to meet up
#Kubecon #CloudNativeFdn #OpenSource #Kubernetes #Nix #Devbox
#Kubecon #CloudNativeFdn #OpenSource #Kubernetes #Nix #Devbox
Reposted by Jetify
This right here is the easiest way I've ever dealt with reproducing bugs.
Someone may use the most exotic OS-level dependency that takes 72 hours to configure properly, yet to reproduce an issue they have I run `devbox shell` and everything is set up.
Someone may use the most exotic OS-level dependency that takes 72 hours to configure properly, yet to reproduce an issue they have I run `devbox shell` and everything is set up.
Best thing about Nix and Devbox is how easy it is to ask for a reproduction.
Just get a copy of the devbox.json, and I can reproduce the user’s exact environment:
www.jetify.com/devbox
Just get a copy of the devbox.json, and I can reproduce the user’s exact environment:
www.jetify.com/devbox
October 26, 2024 at 1:24 PM
This right here is the easiest way I've ever dealt with reproducing bugs.
Someone may use the most exotic OS-level dependency that takes 72 hours to configure properly, yet to reproduce an issue they have I run `devbox shell` and everything is set up.
Someone may use the most exotic OS-level dependency that takes 72 hours to configure properly, yet to reproduce an issue they have I run `devbox shell` and everything is set up.