Introducing OnlyNv

Today, I am pleased to introduce OnlyNv, a platform for peer-to-peer and peer-to-CI¹ syncing of environment variables and secrets.

OnlyNv allows you to take your local .env files, and store them in a centralised location. This allows you to share your environment variables with your team, and keep them in sync across all your CI/CD pipelines.

How it works

OnlyNv stores your environment variables in a centralised, encrypted database.

Whenever you add or update an environment variable, OnlyNv will automatically sync it with your CI/CD pipelines. Furthermore, your team members can pull the latest environment variables directly to their local machines.

Demo

Let's say we have a project, my-project, with the following .env file:

DB_HOST=localhost
DB_USER=root
DB_PASS=password

We want to first create a project on OnlyNv, and then sync our .env file with our GitHub repository.

$ nv init

This will redirect you to the OnlyNv dashboard, where you can create a new project.

You'll now have a new file in your project directory, .lnvrc, which tells the CLI how to sync your environment variables.

We can now use nv link to log in to OnlyNv and sync our environment variables with our CI/CD pipelines.

$ nv link

This will open a browser window, where you can log in to OnlyNv and link your project.

Finally, we can use nv sync to sync our environment variables with the server, and any CI/CD pipelines linked to our project.

$ nv sync

---

OnlyNv is currently in beta, and we are looking for feedback from the community. If you have any suggestions or feature requests, please let us know!

Happy coding!

---

Footnotes

1. Currently, we offer Vercel, GitHub, and Netlify support. More platforms are coming soon. ↩