Using envvar variables that don't start with CKAN
This commit is contained in:
parent
aeda97cfe2
commit
426cd23f25
@ -220,12 +220,13 @@ For the extension to correctly identify which env var keys map to the format use
|
|||||||
|
|
||||||
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
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user