theozero

7 ms·

61.
by theozero 2y ago
also check out https://dmno.dev/docs/plugins/encrypted-vault/
62.
by theozero 2y ago
To be fair, 1password is designed so that they cannot actually access your secrets, and it's likely many of your sensitive secrets are already stored there for use by humans.
63.
by theozero 2y ago
This happens all the time. Pull down the latest and suddenly you've got some cryptic runtime error, and it turns out there's a new config item everyone is missing. Wasting 20 minutes of 10 people's time quickly adds up - and
64.
by theozero 2y ago
We do certainly use JavaScript/TypeScript and we are targeting more JS heavy projects as initial users. That said, DMNO is meant to be universally applicable, and we think javascript is fairly _universal_, even if you personally don&#x
65.
by theozero 2y ago
Thats right :) and yes while you could do something similar on your own, you'd end up building a ton of custom tooling that has nothing to do with your actual business. While DMNO does use vite under the hood, it's not at all tied
66.
by theozero 2y ago
There are tons of debates online about this. Realistically I think it's all tradeoffs and there are no silver bullets, so I won't really weigh in on the _right_ way to do it. But I think we can all agree that MANY people are using
67.
by theozero 2y ago
DMNO founder here - having a proper schema for your config lets us do things like validation, coercion (because env vars are all strings), generate types with built-in docs, and reuse and compose your config together to keep things DRY. It
68.
by theozero 2y ago
DMNO creator here - sensitive config values are able to be retrieved from a variety of backends using a flexible plugin system. We are certainly not telling you that you have to use the encrypted file method, and depending on the security r
69.
by theozero 2y ago
Another new (open source!) tool to check out in this space is https://dmno.dev It's a bit different than most of the other tools listed here, in that it is designed to generally solve the papercuts of dealing with config (b
70.
by theozero 2y ago
I've recently released a comprehensive tool for managing config / env vars - https://dmno.dev . It is the only tool I've seen that natively understands monorepos. This means you can reuse config from the root or ot
71.
by theozero 2y ago
Super early days but we're building something very similar to what you are describing over at https://dmno.dev Granted our solution is more javascript/typescript focused - and the config schema will be defined using Ty