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-deploy
Directory structure and required files
Deploy concatenates a docker-compose command.
docker-compose.yml Required.
docker-compose.deploy.yml Default if no tags are given when running the command.
docker-compose.<tag1>.<tag2>.<etc>.yml Optional. Notice there can be any number of tags.
How to use
deploy [-h] [-d] [-v] [--dry-run] [--flags "<flag1> <flag2>"] [tag]
If a tag is supplied, it will append all parent-tags too, and they are required. I.e. if we
run the command deploy debug.test, it will add (and require) the following three files
docker-compose.yml
docker-compose.debug.yml
docker-compose.debug.test.yml
Notice one can also use the full file as a tag. That is, the following command will give the same result
deploy docker-compose.debug.test.yml.
The first level tag will be used as the project name, i.e. the docker-compose -p command.
Configuration file
An argument string can be saved to a file named .ems-deploy.
The arguments in this string will then automatically be added to the deploy-command.
Additional arguments to the deploy-command will overwrite the commands from the configuration file.
Notes
The following flags are always added to the docker-compose command:
--force-recreate--renew-anon-volumes--build
If the first level tag is deploy, the -d is automatically added.
Deploy
To deploy the app with docker-compose.yml and docker-compose.deploy.yml, simply run
deploy
Additional flags
-dDetaches the process (this is automatically done in deploy-mode, but not in debug-mode)-vWrites the resulting command to the terminal.--dry-runWill not execute the command--flagsChange default flags. Must specify a sting afterwards, e.g.--flags "--force-recreate --build"
Metadata
Release files for ems-deploy 0.0.13
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-deploy-0.0.13.tar.gz | 5.2 kB | Without provenance | Details for ems-deploy-0.0.13.tar.gz |
Release files / ems-deploy-0.0.13.tar.gz
| Download URL | ems-deploy-0.0.13.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddc87ac0edc799a9578fdc69e24fd65edf0de904d47f9c5ea4ca375b1ecda5a0
|
|
BLAKE2b-256 checksum How to use checksums |
e8df2ea2a7ee19f2e6e41260d5d14898eb75904d9667ba72dec191a1cdb04fc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.6.9
|
Security for ems-deploy 0.0.13
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.