Scriptum
A command line utility for storing, documenting, and executing your project's scripts.
Documentation
See documentation here.
A simple use case
With scriptum, you can easily configure scripts into a repo or directory, by placing defining them in a configuration file. Here is an example of a configuration file:
/*
Scripts for my project!
*/
{
"serve": "python3 server.py", // runs the server
"test": { // tests my project
"permissions": { // configures the permissions
"set": "chmod 777 main.py", // makes the executable public
},
"run": "./main.py $1", // runs the executable
"checks": ["mypy **/*.py", "python3 tests/main.py"] // runs the tests
},
"package": { // distribution
"build": "python3 setup.py sdist bdist_wheel", // prepares for release
"publish": "twine upload --repository pypi dist/*" // publishes the package
},
"deps": { // dependency management
"install": ["pip3 install reqs.txt", "brew install pkg"], // installs dependencies
"list": "cat reqs.txt", // lists dependencies
"resolve": "python3 -m pip freeze > main/reqs.txt" // updates the dependency list
},
"docs": { // manage documentation
"install": "npm i -g docsify", // installs docs dependencies
"serve": "docsify serve", // runs the server
"open": "open http://localhost:3000"// opens the preview
}
}
You can now execute any of these scripts conviniently with the scriptum CLI (scr):
scr <script category> <script> <args>
So if you wanted to run the scripts, you can enter the them into the command line like so:
scr help # open index.html
scr deps install # python3 -m pip install requirements.txt
scr deps resolve # python3 -m pip freeze > requirements.txt
scr test permissions set # chmod 777 main.py
scr test run [[production]] # ./main.py 'production'
scr test checks # mypy **/*.py and ./tests/main.py
If you check the configuration file into you repo, your team can now run these scripts with ease.
Features
- Highly configurable
- Cross-platform support
- Supports dependency management from multiple sources (NPM, pip, etc.)
- Script categories
- JSON configuration support for comments and documentation
- Supports command lists that stop on fail
Metadata
Release files for scriptum 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scriptum-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for scriptum-1.0.1-py3-none-any.whl |
Release files / scriptum-1.0.1-py3-none-any.whl
| Download URL | scriptum-1.0.1-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c72f1d6f2aec20e38a83bca7c68b334a54cefe0427a4a620c0f5a85cbe3d0b9
|
|
BLAKE2b-256 checksum How to use checksums |
939babcd969dd770eaf3b1c5fbf7ee64df6bf84f3c01baac0d9618290c9bbb52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.25.1 setuptools/52.0.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.6.4
|
Security for scriptum 1.0.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.