EMS Deploy script
This project provides a general-purpose deploy script for the EMS projects. It runs the suitable docker-compose command based on the available docker-compose files located in the directory.
Install
pip install ems-eploy
Directory structure and required files
Deploy concatenates a docker-compose command. The following files are recognized
docker-compose.ymlRequired: Base filedocker-compose.deploy.ymlRequired: This file is added as an additional docker-compose filedocker-compose.debug.ymlOptional: This files is used instead ofdocker-compose.deploy.ymlwhen using thedebugflag
How to use
The following flags are always added to the docker-compose command:
--force-recreate--renew-anon-volumes--build
Deploy
To deploy the app, simply run
deploy
Note that it will automatically add the -d flag which detaches from the process afterwards.
Debug
To run in debug mode, run
deploy debug
Note that it will NOT automatically detach - this can however be supplied. See the next section for additional flags
Additional flags
-dDetaches the process (this is automatically done in deploy-mode, but not in debug-mode)-vWrites the resulting command to the terminal.
Metadata
Release files for ems-eploy 0.0.5
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 |
|---|---|---|---|---|
| ems-eploy-0.0.5.tar.gz | 2.1 kB | Without provenance | Details for ems-eploy-0.0.5.tar.gz |
Release files / ems-eploy-0.0.5.tar.gz
| Download URL | ems-eploy-0.0.5.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cef598b7b2d83b17025cabfad329e1d94e5fae9552a3283e3b45f4bb0722ea22
|
|
BLAKE2b-256 checksum How to use checksums |
8c04a896ef2bcf14b3b2ed282dad813c8ee159fc8a37aecbf32385808d129206
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.6.9
|
Security for ems-eploy 0.0.5
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.