AI-safe .env files: schemas for agents, secrets for humans.
The internet
Joined February 2024
- Tweets225
- Following260
- Followers370
- Likes572
varlock.dev retweeted
This is pretty cool @varlockdev + 1Password plugin to populate .env files automagically
varlock.dev retweeted
My new "awesome list" of SaaS replacements & tools you can host (for free/$5) on your own @CloudflareDev account has over 800⭐️ in just 1 week!
Can we make it to 1000 before birthday week?
github.com/theoephraim/aweso…
varlock.dev retweeted
I created new repo using @amanvarshney01's Better-Stack just to try out the latest @varlockdev tool
it already created the entire config for me 😭🔥
varlock.dev retweeted
😍 varlock codegen for @EffectTS_ config!
Stoked to see the codegen stuff I added enable new integrations from the community.
@danmyles_ - should we migrate this into the monorepo?
github.com/dan-myles/varlock…
varlock.dev retweeted
Sam, Dario, Elon, @theo and I (also Theo) think @varlockdev is cool as hell.
varlock.dev retweeted
Nothing solves env loading and validation better than Varlock.
Nub v0.7 adds first-party support. If your repo contains an .env.schema file, Nub uses Varlock to load/validate your environment when running a file or script 👇
varlock.dev retweeted
Zod for env validation is a great pattern, and it's super nice to avoid env.d.ts generation
I'm a huge Varlock fan though becuase Varlock solves a bunch of other problems beyond just validation. because it wraps your process, Varlock + .env.schema lets you specify LOADING config in addition to just variable validation. that's why its able to do things like stdio-level redaction, encryption, credential brokering, etc. Zod is just a library so it structurally can't do these things.
I'd also argue from an API design standpoint that Varlock's DSL is strictly better than Zod as a mechanism for validation because it's so finely tuned to the kinds of values & validations you commonly need for env vars
varlock.dev retweeted
my friends @varlockdev have the env var layer covered for those VMs and SDKs
varlock.dev retweeted
If you have starred varlock already, what are you waiting for? Help us get to 5k ⭐️
🧙♂️🔐❤️
varlock.dev retweeted
No need to fear Full Access for your agents.
1. Use macOS TCC (Transparency, Consent, and Control): lock down your agent’s harness so it cannot access your personal data & .app settings
2. Use @varlockdev to stop it getting at your project keys
3. Use @AutomicVault to stop it getting at your CLI tool credentials and to add granular access control for the rest of your dev-tool stack
varlock.dev retweeted
Latest batch of @github secure open source fund is kicking off. This is a great program - provides $10k and deep security training to open source maintainers of important projects.
If you are doing OSS, apply!
(Varlock was in the last batch)
github.blog/open-source/main…
varlock.dev retweeted
Super stoked that nub (as of v0.7) has native varlock support 🚀
Nub does usual .env file loading itself, but if it detects a .env.schema and varlock is installed, it will defer to us instead.
Huge thanks @colinhacks for this and all his work on nub!
nubjs.com/docs/runtime/varlo…
varlock.dev retweeted
Excited to share vlt 1.0 along with our hosted registries & ecosystem mirrors now GA!
A drop-in npm replacement, built so nothing runs on your machine just because you typed install.
→ faster delivery
→ malware blocking at the registry layer
→ graph-native querying – at Toronto, Ontario
varlock.dev retweeted
Yup varlock has been a productivity booster. In dev environment I pair it with keychain access and that makes working in git worktrees such a breeze. No need to add .env files per worktree or even copy them.
varlock.dev retweeted
Varlock is basically types for .env files
It’s another deterministic check you can add to keep your agents from misbehaving
varlock.dev retweeted
Varlock rules. A must have for me