This release is a pre-release and may not be stable for production use.
_
___| |__ ___ _ ____ __
/ __| '_ \ / _ | '_ \ \ / /
| (__| | | | __| | | \ V /
\___|_| |_|\___|_| |_|\_/ . modern local environment management
This command-line interface creates and manages local .env files from various sources.
Coupled with python-dotenv for python, or dotenv for node.js development, it provides better, more consistent environment variable management and developement.
Installation
To install chenv, run this command in your terminal:
$ pip install chenvUsage
chenv’s usage looks like:
$ chenv COMMAND [ARGS]Commands currently include:
blank
Choose to set .env as a new, blank, .env.blank file.
heroku
Choose to set .env from a remote heroku app config-vars, as .env.[app-name].
- -t <team>, --team <team>
Pre-fill team name
- -a <app>, --app <app>
Pre-fill app name
local
Choose to set .env from a local, pre-exsiting .env.* file.
- filename
Pre-fill file-suffix name
Project Configurations
chenv also provides two file types that manipulate the output of new .env.* files being set.
.envignore
Specifies intentionally unwanted environment-variables. Each line in a envignore file specifies a pattern.
When deciding whether to ignore an environment variable, chenv checks it’s key against the list of patterns described in this file.
- Pattern:
.envignore uses the unix filename pattern matching, similar to .gitignore’s, and as specified at https://docs.python.org/3/library/fnmatch.html
.envmerge
Sepecifies environment variables to merge / override after any input is chosen. This provides consistency to preffered settings such as the logging-level, or NODE_ENV for local development usage in node.js.
1 maintainer
Metadata
1 maintainer
Release files for chenv 0.2.2.dev1610358258
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| chenv-0.2.2.dev1610358258.tar.gz | 9.5 kB | Without provenance | Details for chenv-0.2.2.dev1610358258.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chenv-0.2.2.dev1610358258-py3-none-any.whl | Python 3 | none | any | Details for chenv-0.2.2.dev1610358258-py3-none-any.whl |
Total release size: 20.9 kB
Release files / chenv-0.2.2.dev1610358258.tar.gz
| Download URL | chenv-0.2.2.dev1610358258.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f697c428ce2c88c8ee3237631e1e79b0b9848dd43db925905081a14ee2733fc
|
|
BLAKE2b-256 checksum How to use checksums |
d517e2f1e6503da7568d2da66236d55c0e1d388e63d0e35dc214577841a88a07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.7
|
Release files / chenv-0.2.2.dev1610358258-py3-none-any.whl
| Download URL | chenv-0.2.2.dev1610358258-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98ddea836d040e16839419a3c79eb86061112bbd53ee54f39a3ca35dbe01ec1e
|
|
BLAKE2b-256 checksum How to use checksums |
c6257c2f1cd7958e2cd5afa655f8042614b02f9d2765a5adbe29af6a2ee73800
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.7
|
Security for chenv 0.2.2.dev1610358258
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
