barbara

Environment variable management

mathsucks

Python

… image:: https://repository-images.githubusercontent.com/131429006/7eb3f680-8572-11e9-8c3d-68b1476c50e8#

Environment variable management

New in 2.0!

Features have been dropped:
- Legacy templates aren’t supported anymore
- Subvariables aren’t supported anymore
- SSM support has been dropped, as there are better ways to do this
Schema-version has been added to document schema to make it easier for me to deprecate and change the schema if necessary

Installation

… code:: shell

$ pip install barbara

Usage

YAML Format (.env.yml)

Create an .env.yml for your project

… code:: yaml

schema-version: 2
project:
name: your_project
output: env-file

environment:
ENVIRONMENT_NAME: development
DATABASE_URL: postgres://root@db:5432/mydb
DEBUG: 1
MEDIA_DIRS: media,static
CSRF_COOKIE_SECURE: 0

Run barb and you’ll be prompted for the values

… code:: bash

$ barb
env-file does not exist. Create it? [y/N]: y
Creating environment: env-file
Skip Existing: True
DATABASE_URL [postgres://root@db:5432/mydb]: root:[email protected]:5432/sample
ENVIRONMENT_NAME [development]:
Environment ready!

Inspect the generated file, see your values!

… code:: bash

$ cat .env
DATABASE_URL=root:[email protected]:5432/sample
ENVIRONMENT_NAME=development

Why `barbara`?