vertefra / env-manager

Manages .env files

Env Manager

Manages multiple .env files configurations for your project. Configurations are stored encrypted.

Install

Download and install installation script (Only tested on linux)

 curl -sSL https://raw.githubusercontent.com/vertefra/env-manager/master/install.sh | bash

Add a configuration

In order to store a new configuration file you need to add an header to your file. Headers are at the top of the file and are metadata about the file. The identifier identify the configuration when you want to restore it.

example

#- identifier: LOCAL
#- restore-as: .env
STAGE=LOCAL
PEM_KEY=~/Downloads/MyKey.pem
SECRET_KEY=~/Downloads/MyKey.pem

Another header is restore-as which is the name of the file that will be restored. If not provided the file will be restored as .env

Secrets

In order to encrypt and decrypt the configurations you need to generate a secret. Secret is read first from the environment variable ENV_MANAGER_SECRET. If no secret is found, it will try to look into a .secret file in the current directory.

Valid secret is a 16, 24 or 32 bytes long string. If Generating from hexadecimal consider that 2 characters are 1 byte.

Generate a secret in .secret file

openssl rand -hex 16 > .secret

Generate a secret in environment

export ENV_MANAGER_SECRET=$(openssl rand -hex 16)

Usage

Add a new configuration

env-manager add -f .env

Where .env is the file you want to store and contains a valid #- identifier: <config identifier> header

This will add the current configuation present in your .env file to the manager enviroment. The configuration will be identified by the #- identifier header.

Restore a configuration

env-manager get -i <header identifer>

Where <header identifer> is the identifier of the configuration you want to restore.

List all configurations

env-manager list

Shows all the identifiers of the configurations stored in the manager.