Skip to content

Containerized jinja2-cli built on top of Alpine Linux

Notifications You must be signed in to change notification settings

wesley-dean/jinja2-cli

Folders and files

NameName
Last commit message
Last commit date

Latest commit

e43ffea · Mar 26, 2025
Mar 26, 2025
Apr 10, 2024
Mar 25, 2025
Mar 25, 2025
Mar 3, 2025
Feb 15, 2022
Apr 10, 2024
Mar 25, 2025
Jul 2, 2024
Apr 10, 2024
Feb 16, 2022
Oct 7, 2024
Mar 3, 2025
Mar 6, 2025

Repository files navigation

jinja2-cli

Build MegaLinter

This is containerized jinja2-cli built on top of Alpine Linux.

To Use

A convenience wrapper, jinja2-cli is provided to simplify use.

./jinja2-cli template.j2 data.json > output_file

By default, the current directory is bind-mounted to the container so files (and subdirectories) located in the current directory are available to the container. So, for example, this will work:

./jinja2-cli templates/foo.j2.txt data.json > foo.txt

However, this will not:

./jinja2-cli ../templates/foo.j2.txt data.json > foo.txt

Specifying a Directory

In situations like those, the environment variable directory will need to used to indicate a directory that contains all of the files and directories:

directory=../ bin/jinja2-cli templates/foo.j2.txt data/data.json > foo.txt

Specifying a Username

By default, the container runs with the UID of the current user. This ought not be major concern as jinja2-cli does not write to the filesystem by default; it may, however, be an issue if a template or data file isn't readable by the current user.

Command Line Arguments

Arguments passed to jinja2-cli will be passed to the container; these may include files in the container, CLI options, etc..

./jinja2-cli template.j2.txt data.json --format=json

Additional information may be found on the jinja2-cli's README.md: Jinja2-cli Usage

Data Format Support

The containerized application supports the following data formats:

  • ini
  • json
  • querystring
  • yaml
  • yml
  • toml
  • auto

To Build

docker build -t tagname .