From 1f1e8f39c46390d517d3356f3eea9eabf49b12e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Erik=20Pedersen?= Date: Tue, 24 Nov 2020 14:11:42 +0100 Subject: [PATCH] Allow setting the delimiter used for setting config via OS env, e.g. HUGO_ Fixes #7829 --- content/en/getting-started/configuration.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/getting-started/configuration.md b/content/en/getting-started/configuration.md index fda7e2327..d12ecdf3b 100644 --- a/content/en/getting-started/configuration.md +++ b/content/en/getting-started/configuration.md @@ -427,6 +427,8 @@ Names must be prefixed with `HUGO_` and the configuration key must be set in upp To set config params, prefix the name with `HUGO_PARAMS_` {{% /note %}} +{{< new-in "0.79.0" >}} If you are using snake_cased variable names, the above will not work, so since Hugo 0.79.0 Hugo determines the delimiter to use by the first character after `HUGO`. This allows you to define environment variables on the form `HUGOxPARAMSxAPI_KEY=abcdefgh`, using any [allowed](https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names#:~:text=So%20names%20may%20contain%20any,not%20begin%20with%20a%20digit.) delimiter. + {{< todo >}} Test and document setting params via JSON env var. {{< /todo >}}