trask 
Declarative recipe-based task runner
Usage:
python3 -m trask [--dry-run] <path>
Example
docker-build {
tag 'proj1'
from 'amazonlinux:2'
recipes {
yum-install {
pkg [ 'gcc' 'openssl-devel' ]
}
install-rust {
channel 'nightly'
}
}
workdir '/app'
}
docker-run {
image 'proj1'
init true
volumes [
{
host '..'
container '/app'
}
]
commands [
'cargo build --release'
'cargo test --release'
]
}
create-temp-dir {
var 'install-dir'
}
copy {
recipe 'copy'
src [
proj1.service'
'../target/release/proj1'
]
dst install-dir
}
set {
user 'nbishop'
host '12.34.56.78'
identity env(SSH_KEY_PATH')
}
upload {
replace true
identity identity
user user
host host
src install-dir
dst 'app'
}
ssh {
identity identity
user user
host host
commands [
'sudo cp app/proj1.service /etc/systemd/system/'
'sudo systemctl enable proj1'
'sudo systemctl restart proj1'
]
}
Metadata
Release files for trask 1.2.1
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 |
|---|---|---|---|---|
| trask-1.2.1.tar.gz | 7.4 kB | Without provenance | Details for trask-1.2.1.tar.gz |
Release files / trask-1.2.1.tar.gz
| Download URL | trask-1.2.1.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7cecfe6521498eb05abd33dfe8a58bcd906787f016901b3167d44d1b2858b91
|
|
BLAKE2b-256 checksum How to use checksums |
0c9fa2673d48ffbe4bbc49679c951b496553b2e70aa486c5c07231aea7393589
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.1
|
Security for trask 1.2.1
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.