envi retweeted
We are addressing the biggest issue with envi you might have which is trust
“Why would I store my .env variables on someone’s server, even if it’s open source”?
We are working on it
@shellhaki will quote this soon
We are addressing the biggest issue with envi you might have which is trust
“Why would I store my .env variables on someone’s server, even if it’s open source”?
We are working on it
@shellhaki will quote this soon
envi retweeted
Envi is an environmental secrets manager, that serves as the source of truth for what used to be in your .env files
No need for .env files anymore, just either run envi copy in your project root or inject into your program with
envi run —
Eg: envi run — npm start
> injected 20 secrets
No stress, no setup
Plans are simple and tailored for our economy:
Free plan: unlimited projects & environments but only one user per project.(best for solo devs)
PayGo: N600 ($0.40) to add a person to a project (while on free plan)
Teams: N 5,300/month ($4.00) for unlimited everything (best for proper teams/startups/companies
Don’t want to pay anything at all but want to have everything ?
You can self host on your own server.
Site: envisecrets.com
Docs: docs.envisecrets.com
Repo: github.com/shellhaki/envi
Plans are now on envi + every other thing you missed:
You can now copy you envi secrets either from your dashboard or on your terminal with “envi copy”
You can now also directly modify your secrets on terminal with “envi mod”
And lastly plans are now on Envi🎉
You can now copy your env secrets and paste directly into your cloud platform (most parse automatically)
envisecrets.com
Envi beta is finally here 💛
Site: envisecrets.com
Docs: docs.envisecrets.com
Repo: github.com/shellhaki/envi (star if you can!)
Found a bug? [email protected]
Serious bugs may get rewarded.
envi retweeted
Envi is an environment secrets manager built for teams and collaboration.
Here’s a simple scenario:
Haki is collaborating with @honour_can_code on @pxxl_space.
Option A: Without Envi
Honor sends Haki the .env file through WhatsApp.
Later, Honor changes something in the environment variables.
Haki needs the updated .env, so he has to ask Honor to send it again.
Or worse, someone accidentally leaks the .env file.
Now you have secrets floating around in chats, downloads, and random folders.
Option B: With Envi
Honor adds Haki to the Pxxl project’s secrets registry.
Now, whenever Haki makes changes to the environment, he simply runs:
envi push
Honor can then get the latest version with:
envi pull
No sending .env files around. No asking someone to resend the latest version.
And if something goes wrong?
Haki can check the secrets history and restore an earlier version of the environment.
A proper versioning system for secrets is also on the way.
Tamper resistant. Fast. Reliable.
Are you sold yet?
envi.haki.top
