FMF-Jinja
Jinja templating engine using fmf metadata.
Concept
The scope of this project is to take a templated folder and generate multiple output
folders with relation to one another. Consider the following fmf file example in
example/minimal:
var1: 42
var2: Default value
/rootA:
/rootB:
var2: Overwritten
This is interpreted by fmf as:
$ fmf show --path example/minimal
/rootA
var1: 42
var2: Default value
/rootB
var1: 42
var2: Overwritten
These variables (var1, var2) are then used as variables inside a jinja template
creating templated folders under rootA and rootB with their respective values. Try
it out by running
$ fmf-jinja -r example/minimal generate -o /path/to/some/output/folder
To appreciate the full capabilities see the fmf features and jinja template guide. Also check the online documentation for more examples and detailed usage guide.
1 maintainer
Metadata
1 maintainer
Release files for fmf-jinja 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fmf_jinja-0.1.0.tar.gz | 40.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fmf_jinja-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.7 kB
Release files / fmf_jinja-0.1.0.tar.gz
| Download URL | fmf_jinja-0.1.0.tar.gz |
|---|---|
| Size | 40.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd5403f12283cb7dfb6bea04a2474277d798ba6149cf38143258d1525073dd57
|
|
BLAKE2b-256 checksum How to use checksums |
5f814e7acc435f4f9049a398cee3d2fce15210dc614dbfdad06a03e8d0cca92c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2024.
Transparency logRelease files / fmf_jinja-0.1.0-py3-none-any.whl
| Download URL | fmf_jinja-0.1.0-py3-none-any.whl |
|---|---|
| Size | 26.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82a04e8f47a34ccb0385f294068d52ea16f37ab15265bebf5b8c78fa013f0bae
|
|
BLAKE2b-256 checksum How to use checksums |
a015dd9d98ec053a71cd356253b42d484a9bbae077b4cd12a35f9c1a36e4b33b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2024.
Transparency log
