Apart from sad scenarios like this, there is always no sync in changes that happen with env files amongst teams. In some cases, you will probably run the program first or check an env declaration file if it exists for guidelines on how to create your env file. These guidelines do not include the env values or API keys 🤯

These situations can be prevented by using the jsonbank-env cli package.

Requirements

• Nodejs Installed.
• Jsonbank account
• Jsonbank public key.

Getting Started.

Create a new private project on jsonbank or use any existing private project. For this post, we will be using a new project we created called envs

We will also create 3 new files

• default.json
• default-array.json
• prod.json

default.json

{
  "NODE_ENV": "development",
  "PORT": 3000,
  "SSL": null,
  "DB_HOST": "localhost",
  "DB_USER": "root",
  "DB_PASS": "root",
  "DB_NAME": "test"
}

default-array.json

[
  {
    "NODE_ENV": "development",
    "PORT": 3000
  },
  {
    "SSL": null
  },
  {
    "DB_HOST": "localhost",
    "DB_USER": "root",
    "DB_PASS": "root",
    "DB_NAME": "test"
  }
]

prod.json

{
  "NODE_ENV": "production",
  "PORT": 80,
  "SSL": true,
  "DB_HOST": "localhost",
  "DB_USER": "root",
  "DB_PASS": "root",
  "DB_NAME": "test"
}

So your project menu should be looking like this

Generate Config File

Navigate to your local working directory where you want the envs to be imported.

Run

npx jsonbank-env init

This will create your jsonbank.env.json file. This file is where you will set your public key and remote paths to your env files.

Get your Public key

Create a new application on jsonbank and you will be given your public and private keys. Put the public key in your jsonbank.env.json

Set your remote files

Set your config file to look like this

{
  "public_key": "Your public key",
  "envs": {
      "dev": "envs/default.json",
      "dev:formatted: "envs/default-array.json",
      "prod": "envs/prod.json"
   }
}

Fetch Env Files

Get the dev env file and save it as .env

npx jsonbank-env dev .env

Your generated env file should look like

NODE_ENV="development"
PORT=3000
SSL=
DB_HOST="localhost"
DB_USER="root"
DB_PASS="root"
DB_NAME="test"

Get the dev:formatted env file and save it as .neat.env

npx jsonbank-env dev:formatted .neat.env

Your generated env file should look like this with neat spacing because the json content is an array of objects. Each object in the array is automatically separated with a new line.

NODE_ENV="development"
PORT=3000

SSL=

DB_HOST="localhost"
DB_USER="root"
DB_PASS="root"
DB_NAME="test"

Now try the last one for prod env file. it should generate an env with NODE_ENV=production

We hope you find this service as useful as we did. For more info, see the npm package documentation

New File Manager

The new Project File Manager gives a table view of your files and folders. This is necessary when files get up to 1000+ in a folder. 🧐 You will have paginated results of your files and folder 25/25 respectively with a load more button for folders and a numbered pagination for files. 😁

Watch Project

Before now you could only get event alerts on files for file.updated and file.deleted events.

Now, you can watch a project for events that happens in a project via webhooks

The events currently supported are

• file.created => Fires when a new file is created.
• file.updated=> Fires when any file in the project is updated.
• file.deleted => Fires when any file in the project is deleted.

Json to Env

A node CLI package to load your env variables from the cloud. See the blog post about it here: Load your env from the cloud