** A simple example of a vertically app merged grains project **
INSTALLATION
With git:
git clone https://gitlab.com/saltstack/pop/grains.git pip install -e grains
With pip:
pip install corn_cowsay
EXECUTION
After installation the grains command should now be available if it wasn’t already
TESTING
install requirements-test.txt with pip and run pytest:
pip install -r grains/requirements-test.txt pytest grains/tests
VERTICAL APP-MERGING
Instructions for extending grains like this project does
Install pop:
pip install --upgrade pop
Create a new directory for the project:
mkdir grains_{project}
cd grains_{project}
Use pop-seed to generate the structure of a project that extends grains:
pop-seed -t v pop_{kernel} -d grains
“-t v” specifies that this is a vertically app-merged project
“-d grains” says that we want to implement the dynamic name of “grains”
Add “grainsv2” to the requirements.txt:
echo "grainsv2" >> requirements.txt
Note* url based reqs aren’t supported on older versions of setuptools To pip install your vertically app-merged project install grains manually:
pip install -e git+https://gitlab.com/saltstack/pop/grains.git#egg=grainsv2
And that’s it! Go to town extending grains Follow the conventions you see in gitlab.com/satlstack/pop/grains
Metadata
Release files for grains-cow-fortune 2
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 |
|---|---|---|---|---|
| grains-cow-fortune-2.tar.gz | 3.4 kB | Without provenance | Details for grains-cow-fortune-2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| grains_cow_fortune-2-py3-none-any.whl | Python 3 | none | any | Details for grains_cow_fortune-2-py3-none-any.whl |
Total release size: 6.2 kB
Release files / grains-cow-fortune-2.tar.gz
| Download URL | grains-cow-fortune-2.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc9371d593c0b9a28c9934f431de0a5e5fe91b3447d61d0d0a7170a8087c8961
|
|
BLAKE2b-256 checksum How to use checksums |
2669cbbba08b38451b53a0a28575a63c5d868a9cf455b81fe4bf57ea4e61d24e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
Release files / grains_cow_fortune-2-py3-none-any.whl
| Download URL | grains_cow_fortune-2-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ef0a61908f3f2774baa2abae9c7b583735f46eb1580e4145eb4705054e05bc5
|
|
BLAKE2b-256 checksum How to use checksums |
4903f4ae283203733d8e37bcf97e69f29a86c05c9737f09316b9ce3b004d07e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
Security for grains-cow-fortune 2
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.