From 426cd23f25b055f785f9d4091563b410af51708d Mon Sep 17 00:00:00 2001 From: Alasdair Gray Date: Tue, 20 Jun 2023 17:09:38 +0100 Subject: [PATCH] Using envvar variables that don't start with CKAN --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 6b1931c..ffdfaf3 100644 --- a/README.md +++ b/README.md @@ -218,14 +218,15 @@ This extension checks for environmental variables conforming to an expected form For the extension to correctly identify which env var keys map to the format used for the config object, env var keys should be formatted in the following way: - All uppercase - Replace periods ('.') with two underscores ('__') - Keys must begin with 'CKAN' or 'CKANEXT' + All uppercase + Replace periods ('.') with two underscores ('__') + Keys must begin with 'CKAN' or 'CKANEXT', if they do not you can prepend them with '`CKAN___`' For example: * `CKAN__PLUGINS="envvars image_view text_view recline_view datastore datapusher"` * `CKAN__DATAPUSHER__CALLBACK_URL_BASE=http://ckan:5000` + * `CKAN___BEAKER__SESSION__SECRET=CHANGE_ME` These parameters can be added to the `.env` file