Travis A. Everett
@abathur
Anyone interested in nix, shell, or markup+documentation? Debating whether to discuss any of the OSS work I've been doing the past few years.
1 reply
0 recast
1 reaction
Yousuf Haque
@yousufhaque.eth
Yes definitely. I’m at a small startup but we’re running into friction trying to keep environment variables for everyone in sync. Also touching on syncing required binaries across machines like protoc or the rust tool chain. Docker + gcloud secrets manager makes sense but am curious about using nix instead
1 reply
0 recast
1 reaction
Travis A. Everett
@abathur
What kind of product and stack? Can you give a couple example of the envs you need to sync?
1 reply
0 recast
1 reaction
Yousuf Haque
@yousufhaque.eth
Things like api keys for both staging and dev, urls for services that a mobile app running in an emulator can hit, database connection strings We’re deploying typescript and rust apps to containers on gcp along with some other typescript services to Cloudflare workers.
2 replies
0 recast
0 reaction
Travis A. Everett
@abathur
I haven't needed to do too much secrets stuff, but Nix can help standardize the environment. Most of our secret cases so far have been things that we can readily generate/rotate or mirror from prod via CLI. I think most people are using agenix or sops-nix for this bit.
1 reply
0 recast
1 reaction
Travis A. Everett
@abathur
If you don't have a resident Nix-er, I'd explore via higher-level projects focused on this case: floxdev.com, devenv.sh, github.com/nickel-lang/organist, jetpack.io/devbox/. Unfortunately haven't used these yet so I can't narrow. The organist README briefly compares all of these.
1 reply
0 recast
1 reaction
Yousuf Haque
@yousufhaque.eth
All of these look pretty neat. I’ll look into these and report back what works best
1 reply
0 recast
1 reaction
Yousuf Haque
@yousufhaque.eth
Though I did plan on becoming the resident nixer
0 reply
0 recast
1 reaction
