Eco allows you and your team to effortlessly and securely share non-production environment variables, without the overhead of setting up dedicated secrets servers.

What's this for?

Have you ever...

• Had a local .env file get deleted or corrupted, causing you to lose environment variables?
• Worked on a team with disorganized or superfluous environment variables?
• Wanted an easy way to securely share environment variables with other project maintainers without need to set up 3rd party secrets management?
• Wanted your team to be able to easily pull an up-to-date copy of project config?

If you answered "yes" to any of these then Eco is for you!

Important: Eco is not a secure mechanism for storing and sharing production-level environment variables. It's not. Please don't.

How it works

Eco is actually pretty simple. It operates using 3 different storage mechanisms:

1. Your project .env file. This is where the values you're actually using live, because your project depends on them.
2. Your local "vault". The vault is a local config file where you can permanently store any environment variable you don't want to lose. This gives you the ability to nuke your .env file and then just pull in the keys you want to restore.
3. The remote .eco file. When you push keys you want shared by the team, Eco creates an .eco file in the root of your repo, directly in the master branch. Inside the .eco file are your shared keys, all encrypted using the same strategy used by Github when storing repository secrets. This file will store unique key:value pairs that your team pushes to it.

Documentation

Installation

Eco CLI may be installed globally or on a per-project basis using Composer:

$ composer require hotmeteor/eco-cli
 
$ composer global require hotmeteor/eco-cli

Getting Started

Once Eco is installed it needs to be set up. Ideally, this is done within the folder for the project you are collaborating on.

There are different setups depending on what code host your team uses.

Github

Github requires a personal access token.

1. Create a Github Personal Access Token is required.
   • Choose repo and read:org permissions

Gitlab

Gitlab requires a personal access token and a Deploy Key.

1. Create a Personal Access Token: https://gitlab.com/profile/personal_access_tokens
   • Choose api privileges
2. Create a Deploy Key for your project: https://gitlab.com/[group]/[project]/-/settings/repository
   • Name it eco-cli
   • Make sure "Write access allowed" is checked

Bitbucket

Bitbucket requires an App Password and an Access Key.

1. Create an App Password: https://bitbucket.org/account/settings/app-passwords/
   • Select:
     • Account Email, Read
     • Project Read
     • Repositories Read, Write, Admin
2. Create an Access Key for your project: https://bitbucket.org/[workspace]/[project]/admin/access-keys/
   • Name it eco-cli
3. When authenticating Eco, your credentials will be your typical Bitbucket username and your new app password.

Usage

Eco comes with a number of commands to manage local and remote environment variables.

Setup

$ eco init

The first thing you run after installing.

You will be asked to select the code host your team uses, as well as provide the proper credentials. You will then be asked to select the owner or organization to act under, as well as the repository for the current project.

$ eco vault

View all the values in your Vault.

Organizations

$ eco org:switch

List available organizations you're a member of and allow you switch to a different one.

$ eco org:current

Show the current working organization.

Repositories

$ eco repo:list

List available repositories in your organization.

$ eco repo:switch

List available repositories in your organization and allow you switch to a different repo. This allows you to use Eco across different repositories. Just don't forget to switch repos before pushing or pulling!

$ eco repo:current

Show the current working repository.

Keys

$ eco env:fresh

Fetch the .env.example file from your project repository and copy it as your new local .env file. This is a desctructive command, so you are asked to confirm.

$ eco env:set

Create or update a key:value pair in your local vault and will add it to your local .env file.

$ eco env:unset

Remove a key:value pair from your local vault and will remove it from your local .env file.

$ eco env:push

Push a key:value pair into the remote .eco file.

$ eco env:sync

Sync all key:value pairs from the remote .eco file with your local .env file. You will be asked to confirm before overwriting any local values with remote values.

Contributing

If you're interested in contributing to Eco, please read our contributing guide.

Acknowledgments

Built on the fantastic Laravel Zero framework by @nunomaduro

Inspired by the work done on the Vapor CLI, which provided some foundational code for this CLI.