domenkozar

5 ms·

31.
Where .env Went Wrong(secretspec.dev)
99 points by domenkozar 2mo ago|69 comments
32.
Devenv 2.2: attach to running processes and persistent out-of-tree environments(devenv.sh)
4 points by domenkozar 2mo ago|0 comments
33.
SecretSpec 0.17: Scopes, secrets caching, SOPS, age, and systemd credentials(secretspec.dev)
3 points by domenkozar 2mo ago|0 comments
34.
But I Use SOPS(secretspec.dev)
1 points by domenkozar 2mo ago|0 comments
35.
Secrets Don't Belong in Config(secretspec.dev)
19 points by domenkozar 3mo ago|5 comments
36.
SecretSpec 0.15: Provider Credentials, Azure Key Vault / Gopass, and PHP SDK(secretspec.dev)
2 points by domenkozar 3mo ago|0 comments
37.
by domenkozar 3mo ago
Rust, mostly because: - haskell exceptions and laziness are devastating for production - too small ecosystem, had to write 10+ SDKs (now with AI that's less of an issue) - haskell ecosystem is too fragmented due to prima donna prevalen
38.
by domenkozar 3mo ago
We at Cachix have also moved on from Haskell about two years ago and I'm sure someone is going to make a comeback with a language that takes the lessons from it but starts from skratch. We need more general purpose Elm languages in the
39.
SecretSpec 0.13: SDKs for Python, Node.js, Go, Ruby, and Haskell(secretspec.dev)
3 points by domenkozar 3mo ago|0 comments
40.
Making devenv start fast, and the whole nixpkgs with it(devenv.sh)
2 points by domenkozar 3mo ago|0 comments
41.
SecretSpec 0.12: audit logs and coding agents(secretspec.dev)
3 points by domenkozar 4mo ago|0 comments
42.
Devenv 2.1: Nix with native support for zsh, fish, and nushell via libghostty(devenv.sh)
6 points by domenkozar 5mo ago|1 comments
43.
by domenkozar 7mo ago
We see project specific environments superior to having global packages installed. You can do things like creating ad-hoc environments: $ devenv -O languages.rust.enable:true shell Once you teach your coding agent to use it, it will just us
44.
by domenkozar 8mo ago
We're going to see more social networks struggle and something like world.org or similar that protects privacy is needed.
45.
by domenkozar 10mo ago
What if GitHub Actions were local-first and built using Nix (proper locking)? https://github.com/cachix/cloud.devenv.sh
46.
Devenv 1.11: Module changelogs and SecretSpec 0.4.0(devenv.sh)
1 points by domenkozar 10mo ago|0 comments
47.
by domenkozar 11mo ago
You guys need to figure out how to create Slack shared channels in Zed and we're all switching until they won't be needed anymore.
48.
by domenkozar 11mo ago
Look at the problem statement, it's exactly the same. When I designed secretspec, I researched the space and no other tool approached secrets in such a way. Syntax of toml is almost identical, the CLI as well. It even has the same voca
49.
Devenv 1.10: monorepo Nix support with devenv.yaml imports(devenv.sh)
3 points by domenkozar 1y ago|0 comments
50.
Ephemeral Win11 testing VM for a few bucks per month(paretosecurity.com)
3 points by domenkozar 1y ago|0 comments
51.
by domenkozar 1y ago
I'm really excited about what teams will build using profiles, they enable all kinds of cool things.
52.
Devenv 1.9: Scaling Nix projects using modules and profiles(devenv.sh)
11 points by domenkozar 1y ago|1 comments
53.
by domenkozar 1y ago
We're aiming to take Nix to its most simple form, while devbox uses json for configuration. Think of devenv as systemd of developer environments.
54.
by domenkozar 1y ago
Yes, it does vendor all the crates to Nix store. It results into speed up in a way that if your application doesn't change, you'll just get the binary package. That's why the two interfaces are exposed: one for development fe
55.
Closing the Nix gap: From environments to packaged applications for rust(devenv.sh)
82 points by domenkozar 1y ago|46 comments
56.
From Frustration to Power: What We Learned at Nixcademy(lobste.rs)
2 points by domenkozar 1y ago|0 comments
57.
Devenv 1.8: Progress TUI, SecretSpec, Listing Tasks, and Smaller Containers(devenv.sh)
5 points by domenkozar 1y ago|0 comments
58.
by domenkozar 1y ago
I'll reply, even though I don't like the tone the first sentance sets :) I'm not sure exactly what parts of the comment are about secrets rather than how infrastructure should be done, but I see that secrets and configuration
59.
by domenkozar 1y ago
I'm not advocating that different locations of secrets IS something we want, but rather it IS the sad state of reality. By having a secrets specification we can start working towards a future that will consolidate these providers and a
60.
by domenkozar 1y ago
The example is more of a way to show how to keep backwards compatibility and migration to secretspec. We hope that one day github actions would integrate secretspec more tightly, leaving aside using environment variables as a transport. Tha

More ›