start_ckan.sh replaces the api_token.jwt.encode.secret and api_token.jwt.decode.secret values when the beaker.session.secret is empty (which it is by default).
I understand that one can set these values in the .ckan-env file, but I don't understand why that is needed? If you let ckan just create its config (ckan generate config) these keys get a default value. Why not keep that default value and only overwrite through env vars when it is not sufficient?
start_ckan.sh
replaces theapi_token.jwt.encode.secret
andapi_token.jwt.decode.secret
values when thebeaker.session.secret
is empty (which it is by default).I understand that one can set these values in the
.ckan-env
file, but I don't understand why that is needed? If you letckan
just create its config (ckan generate config
) these keys get a default value. Why not keep that default value and only overwrite through env vars when it is not sufficient?