Environment variable management
- 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
$ pip install barbara- Create an
.env.ymlfor your project
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
barband you'll be prompted for the values
$ 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!
$ cat .env
DATABASE_URL=root:[email protected]:5432/sample
ENVIRONMENT_NAME=developmentBecause Barbara Liskov created the Liskov Substitution Principle and is a prolific contributor to computer science and software engineering. Barbara is one of the Newton's metaphorical giants that enables us to see further. I humbly dedicate my project to her and her contributions and offer this project to its consumers with a license befitting that dedication.
