Back to #solodad. On my way to pick up the kids. Daughter has gymnastics today.

Finished writing up a guide on how to use dotenvx with AWS Lambda dotenvx.com/docs/platforms…

Spent the first half of the day taking the California Boater Card class and passing the test. For the afternoon, I've been polishing dotenvx and dotenvx-pro. Lots of work to do on Pro's cloak command still.

gm

Been working today on tightening up the [dotenvx pro cloak] command. It's going to be the first experience of dotenvx pro. How it goes will go a long ways to how much someone gets that early 'ah ah' moment for dotenvx pro. Cloaked (fully managed private) keys.

I can't wait to pound the pavement and start selling Pro. It's going to be an incredible product. It's going to compete with the big dog Hashicorp Vault. I think we have a far more attractive flow for how developers actually work – and I think I'm close to being able to tell the

ok, dotenvx pro cloak command is now working pretty well. shifting to the extension - so that you can be browsing your pull request and decrypt the values with a click.

[dotenvx week over week] 👀 views: 11.1 (-0.6k, -5%) 🧑‍💻 people: 2.5k (-0.1k, -4%) 📦 npm: 444k (+31k, +7.5%) 🔗 usedby: 6,069 (+411, +7%) 📝 vscode: 524 (+25, +5%) [interesting new used by] eulerstream [1], reddit [2] [mentions] devto [2]

Adding devices to dotenvx pro today. So that your userPrivateKey is encrypted per device level. This will also unlock better syncing between devices like your chrome extension (for GitHub PR review of encrypted .env files) and your cli (for managing them).

[dotenvx week over week] 👀 views: 12.5 (+0.6k, +5%) 🧑‍💻 people: 2.6k (flat) 📦 npm: 429k (-9k, -2%) 🔗 usedby: 7,015 (+277, +4%) 📝 vscode: 623 (+37, +6%) [interesting new used by] chainflip [1], nn lang [2] [mentions] hacker news [3], reddit [4] [1] chainflip.io