makejinja 2.3.0__tar.gz → 2.3.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {makejinja-2.3.0 → makejinja-2.3.1}/PKG-INFO +9 -9
- {makejinja-2.3.0 → makejinja-2.3.1}/README.md +8 -8
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/__init__.py +2 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/pyproject.toml +1 -1
- {makejinja-2.3.0 → makejinja-2.3.1}/LICENSE +0 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/__main__.py +0 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/app.py +0 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/cli.py +0 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/config.py +0 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/loader.py +0 -0
- {makejinja-2.3.0 → makejinja-2.3.1}/makejinja/py.typed +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: makejinja
|
|
3
|
-
Version: 2.3.
|
|
3
|
+
Version: 2.3.1
|
|
4
4
|
Summary: makejinja is a CLI tool and Python library to automatically generate files from Jinja2 templates. Use it to easily generate complex Home Assistant dashboards!
|
|
5
5
|
Home-page: https://mirkolenz.github.io/makejinja/
|
|
6
6
|
License: MIT
|
|
@@ -39,12 +39,12 @@ Description-Content-Type: text/markdown
|
|
|
39
39
|
|
|
40
40
|
<!-- markdownlint-disable MD033 MD041 -->
|
|
41
41
|
<p align="center">
|
|
42
|
-
<img width="256px" src="
|
|
42
|
+
<img width="256px" src="https://raw.githubusercontent.com/mirkolenz/makejinja/main/assets/logo.png" />
|
|
43
43
|
</p>
|
|
44
44
|
<p align="center">
|
|
45
45
|
<a href="https://pypi.org/project/makejinja/">PyPI</a> |
|
|
46
46
|
<a href="https://mirkolenz.github.io/makejinja">Docs</a> |
|
|
47
|
-
<a href="
|
|
47
|
+
<a href="https://github.com/mirkolenz/makejinja/tree/main/tests/data">Example</a> |
|
|
48
48
|
<a href="https://jinja.palletsprojects.com/en/3.1.x/templates">Templating</a>
|
|
49
49
|
</p>
|
|
50
50
|
<p align="center">
|
|
@@ -61,7 +61,7 @@ This allows you to load variables from external files or create repeating patter
|
|
|
61
61
|
It is conceptually similar to [gomplate](https://github.com/hairyhenderson/gomplate), but is built on Python and Jinja instead of Go.
|
|
62
62
|
A use case for this tool is generating config files for [Home Assistant](https://www.home-assistant.io/):
|
|
63
63
|
Using the same language that the built-in templates use, you can greatly simplify your configuration.
|
|
64
|
-
An [example for Home Assistant](
|
|
64
|
+
An [example for Home Assistant](https://github.com/mirkolenz/makejinja/tree/main/tests/data) can be found in the tests directory.
|
|
65
65
|
|
|
66
66
|
## Features
|
|
67
67
|
|
|
@@ -72,7 +72,7 @@ An [example for Home Assistant](./tests/data) can be found in the tests director
|
|
|
72
72
|
- Tailor the whitespace behavior to your needs.
|
|
73
73
|
- Use custom delimiters for Jinja blocks/comments/variables.
|
|
74
74
|
- Modify _all_ init options for the Jinja environment.
|
|
75
|
-
- Write custom **Python loaders** that implement a subset of our fully typed [abstract loader class](
|
|
75
|
+
- Write custom **Python loaders** that implement a subset of our fully typed [abstract loader class](https://mirkolenz.github.io/makejinja/makejinja/loader.html#AbstractLoader)
|
|
76
76
|
|
|
77
77
|
## Installation
|
|
78
78
|
|
|
@@ -92,25 +92,25 @@ Thus, we advise leveraging [`pipx`](https://github.com/pypa/pipx) instead:
|
|
|
92
92
|
|
|
93
93
|
You can then directly invoke the app as follows:
|
|
94
94
|
|
|
95
|
-
`makejinja
|
|
95
|
+
`makejinja -i ./input -o ./output`
|
|
96
96
|
|
|
97
97
|
### Nix
|
|
98
98
|
|
|
99
99
|
If you use the `nix` package manager, you can add this repository as an input to your flake and use `makejinja.packages.${system}.default`.
|
|
100
100
|
You can also run it directly
|
|
101
101
|
|
|
102
|
-
`nix run github:mirkolenz/makejinja --
|
|
102
|
+
`nix run github:mirkolenz/makejinja -- -i ./input -o ./output`
|
|
103
103
|
|
|
104
104
|
### Docker
|
|
105
105
|
|
|
106
106
|
We automatically publish an image at `ghcr.io/mirkolenz/makejinja`.
|
|
107
107
|
To use it, mount a folder to the container and pass the options as the command.
|
|
108
108
|
|
|
109
|
-
`docker run --rm -v $(pwd)/data:/data ghcr.io/mirkolenz/makejinja:latest
|
|
109
|
+
`docker run --rm -v $(pwd)/data:/data ghcr.io/mirkolenz/makejinja:latest -i /data/input -o /data/output`
|
|
110
110
|
|
|
111
111
|
## Usage in Terminal / Command Line
|
|
112
112
|
|
|
113
113
|
In its default configuration, makejinja searches the input folder recursively for files ending in `.jinja`.
|
|
114
114
|
It then renders these files and writes them to the output folder, preserving the directory structure.
|
|
115
|
-
Our [documentation](https://mirkolenz.github.io/makejinja/cli.html) contains a detailed description of all options and can also be accessed via `makejinja --help`.
|
|
115
|
+
Our [documentation](https://mirkolenz.github.io/makejinja/makejinja/cli.html) contains a detailed description of all options and can also be accessed via `makejinja --help`.
|
|
116
116
|
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
<!-- markdownlint-disable MD033 MD041 -->
|
|
2
2
|
<p align="center">
|
|
3
|
-
<img width="256px" src="
|
|
3
|
+
<img width="256px" src="https://raw.githubusercontent.com/mirkolenz/makejinja/main/assets/logo.png" />
|
|
4
4
|
</p>
|
|
5
5
|
<p align="center">
|
|
6
6
|
<a href="https://pypi.org/project/makejinja/">PyPI</a> |
|
|
7
7
|
<a href="https://mirkolenz.github.io/makejinja">Docs</a> |
|
|
8
|
-
<a href="
|
|
8
|
+
<a href="https://github.com/mirkolenz/makejinja/tree/main/tests/data">Example</a> |
|
|
9
9
|
<a href="https://jinja.palletsprojects.com/en/3.1.x/templates">Templating</a>
|
|
10
10
|
</p>
|
|
11
11
|
<p align="center">
|
|
@@ -22,7 +22,7 @@ This allows you to load variables from external files or create repeating patter
|
|
|
22
22
|
It is conceptually similar to [gomplate](https://github.com/hairyhenderson/gomplate), but is built on Python and Jinja instead of Go.
|
|
23
23
|
A use case for this tool is generating config files for [Home Assistant](https://www.home-assistant.io/):
|
|
24
24
|
Using the same language that the built-in templates use, you can greatly simplify your configuration.
|
|
25
|
-
An [example for Home Assistant](
|
|
25
|
+
An [example for Home Assistant](https://github.com/mirkolenz/makejinja/tree/main/tests/data) can be found in the tests directory.
|
|
26
26
|
|
|
27
27
|
## Features
|
|
28
28
|
|
|
@@ -33,7 +33,7 @@ An [example for Home Assistant](./tests/data) can be found in the tests director
|
|
|
33
33
|
- Tailor the whitespace behavior to your needs.
|
|
34
34
|
- Use custom delimiters for Jinja blocks/comments/variables.
|
|
35
35
|
- Modify _all_ init options for the Jinja environment.
|
|
36
|
-
- Write custom **Python loaders** that implement a subset of our fully typed [abstract loader class](
|
|
36
|
+
- Write custom **Python loaders** that implement a subset of our fully typed [abstract loader class](https://mirkolenz.github.io/makejinja/makejinja/loader.html#AbstractLoader)
|
|
37
37
|
|
|
38
38
|
## Installation
|
|
39
39
|
|
|
@@ -53,24 +53,24 @@ Thus, we advise leveraging [`pipx`](https://github.com/pypa/pipx) instead:
|
|
|
53
53
|
|
|
54
54
|
You can then directly invoke the app as follows:
|
|
55
55
|
|
|
56
|
-
`makejinja
|
|
56
|
+
`makejinja -i ./input -o ./output`
|
|
57
57
|
|
|
58
58
|
### Nix
|
|
59
59
|
|
|
60
60
|
If you use the `nix` package manager, you can add this repository as an input to your flake and use `makejinja.packages.${system}.default`.
|
|
61
61
|
You can also run it directly
|
|
62
62
|
|
|
63
|
-
`nix run github:mirkolenz/makejinja --
|
|
63
|
+
`nix run github:mirkolenz/makejinja -- -i ./input -o ./output`
|
|
64
64
|
|
|
65
65
|
### Docker
|
|
66
66
|
|
|
67
67
|
We automatically publish an image at `ghcr.io/mirkolenz/makejinja`.
|
|
68
68
|
To use it, mount a folder to the container and pass the options as the command.
|
|
69
69
|
|
|
70
|
-
`docker run --rm -v $(pwd)/data:/data ghcr.io/mirkolenz/makejinja:latest
|
|
70
|
+
`docker run --rm -v $(pwd)/data:/data ghcr.io/mirkolenz/makejinja:latest -i /data/input -o /data/output`
|
|
71
71
|
|
|
72
72
|
## Usage in Terminal / Command Line
|
|
73
73
|
|
|
74
74
|
In its default configuration, makejinja searches the input folder recursively for files ending in `.jinja`.
|
|
75
75
|
It then renders these files and writes them to the output folder, preserving the directory structure.
|
|
76
|
-
Our [documentation](https://mirkolenz.github.io/makejinja/cli.html) contains a detailed description of all options and can also be accessed via `makejinja --help`.
|
|
76
|
+
Our [documentation](https://mirkolenz.github.io/makejinja/makejinja/cli.html) contains a detailed description of all options and can also be accessed via `makejinja --help`.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
[tool.poetry]
|
|
2
2
|
name = "makejinja"
|
|
3
|
-
version = "2.3.
|
|
3
|
+
version = "2.3.1"
|
|
4
4
|
description = "makejinja is a CLI tool and Python library to automatically generate files from Jinja2 templates. Use it to easily generate complex Home Assistant dashboards!"
|
|
5
5
|
authors = ["Mirko Lenz <mirko@mirkolenz.com>"]
|
|
6
6
|
license = "MIT"
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|