The distroless cc base image includes only what's required to run compiled rust binaries,
see [1] for more info about these images.
Using this base image lets us get rid of dockerize and its build steps and dependencies, including python.
On top of that it provides ca-certificates, timezone data, and other necessary infrastructure.
[1]: https://github.com/GoogleContainerTools/distrolessFixes#1642
* Pass lang to shortcodes context
* Add tests for lang in shortcodes
* Lang is passed to anchor-link.html template
* Document passing lang to shortcodes/anchor-link.html
Add a test to make sure lang can be overriden by passing an explicit argument to the shortcode,
for usage in the markdown filter where the language context is not available.
* Update docs for more information on shortcodes+i18n+markdown() filter
Co-authored-by: southerntofu <southerntofu@thunix.net>
* Next version
* Added ask prompt for output-dir flag
Added `ask_bool` prompt for `--output-dir` for when the output directory
targeted already exists in the file system.
[Issue: #1378]
* Updated the documentation for #1378
* Added missing "sure" in prompt text
* Added timeout to prompt + dirname
* Fixed complication errors
Co-authored-by: Vincent Prouillet <balthek@gmail.com>
After much trial and error, it would seem that the correct location for extra syntaxes is actually the markdown section rather than the main section. This commit fixes that part of the docs.
* Consider the site's output path in search_for_file
The search_for_file helper function now accepts an optional
output path. If passed, the file will also be searched there.
This is used in the get_url function to search in the
Site::output_path.
In practice, this means cachebust works for files in the
output path.
* Make output_dir required in search_for_file
* Update docs for file searching logic
* Add test for new file searching behavior
* cargo/manifests: allow user to use native-tls ...
... if `ring` can't be used on the user's platform (e.g. mips/ppc/riscv)
* CI: test for native tls build
* Briefly explain TOML tables
There's a warning about a possible source of errors, but it doesn't give you the relevant information to actually make sense of it. I hope this saves someone a search since I personally had to find this out reading the TOML spec.
Any other ways to phrase this?
* Update configuration.md
