gitea/ckan
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Using envvar variables that don't start with CKAN

Browse Source
This commit is contained in:
Alasdair Gray 2023-06-20 17:09:38 +01:00 committed by GitHub
parent aeda97cfe2
commit 426cd23f25
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -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: 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 All uppercase
Replace periods ('.') with two underscores ('__') Replace periods ('.') with two underscores ('__')
Keys must begin with 'CKAN' or 'CKANEXT' Keys must begin with 'CKAN' or 'CKANEXT', if they do not you can prepend them with '`CKAN___`'
For example: For example:
* `CKAN__PLUGINS="envvars image_view text_view recline_view datastore datapusher"` * `CKAN__PLUGINS="envvars image_view text_view recline_view datastore datapusher"`
* `CKAN__DATAPUSHER__CALLBACK_URL_BASE=http://ckan:5000` * `CKAN__DATAPUSHER__CALLBACK_URL_BASE=http://ckan:5000`
* `CKAN___BEAKER__SESSION__SECRET=CHANGE_ME`
These parameters can be added to the `.env` file These parameters can be added to the `.env` file