You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Passwords are hardcoded in the .env file which is then used by docker compose to populate environment variables used in the running containers. These passwords are therefore pretty insecure. Therefore I propose to create a process to generate random secure passwords before the local images are built and before the containers start
The following environment variables will use the passwords generated
POSTGRES_PASSWORD
CKAN_DB_PASSWORD
DATASTORE_READONLY_PASSWORD
CKAN_SYSADMIN_PASSWORD
The passwords will be housed in a newly generated file which will have it's permissions locked down to just read-only by the file owner. This file (named .pw) can then be added to both ckan and db services in the docker-compose.yml file as follows:
The text was updated successfully, but these errors were encountered:
I originally commented in #76 (comment) but this is probably better:
If we are doing this work on random passwords, to bypass having passwords in .env files, perhaps it is worth exploring the docker solution for secrets, which works with docker compose:
Passwords are hardcoded in the
.env
file which is then used by docker compose to populate environment variables used in the running containers. These passwords are therefore pretty insecure. Therefore I propose to create a process to generate random secure passwords before the local images are built and before the containers startThe following environment variables will use the passwords generated
POSTGRES_PASSWORD
CKAN_DB_PASSWORD
DATASTORE_READONLY_PASSWORD
CKAN_SYSADMIN_PASSWORD
The passwords will be housed in a newly generated file which will have it's permissions locked down to just read-only by the file owner. This file (named
.pw
) can then be added to both ckan and db services in thedocker-compose.yml
file as follows:The text was updated successfully, but these errors were encountered: