2020-09-17 11:43:24 +02:00
|
|
|
### Please note that this re-purposed CKAN Docker repo is a WORK IN PROGRESS ###
|
2020-09-17 14:02:02 +02:00
|
|
|
### It should not be used to install CKAN via Docker until this page is updated ###
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Potential ideas/investigations from Keitaro (Marko Bocevski) : https://github.com/keitaroinc/docker-ckan:
|
|
|
|
|
|
|
|
|
|
- Maybe use build/up time variables loaded via the .env file, runtime variables loaded via a .ckan-env file - both
|
|
|
|
|
located at the root directory
|
|
|
|
|
- Should we use wheels too?
|
|
|
|
|
- 2 networks: 1) Frontend 2) Backend
|
2020-10-07 16:42:24 +02:00
|
|
|
- Create/access a CKAN datapusher image rather than build one?
|
2020-09-17 14:02:02 +02:00
|
|
|
- all username/passwords as environment variables rather than hardcoded
|
|
|
|
|
- "/images" is a good folder name to use to be able to build all versions of CKAN and DataPusher images
|
2020-09-17 14:59:42 +02:00
|
|
|
- include an "/examples" folder for examples of adding extentions xloader, harvester, etc
|
2020-10-07 16:42:24 +02:00
|
|
|
|
2020-09-25 15:26:15 +02:00
|
|
|
- make sure the "development mode" path is taken cared of with any changes
|
2020-09-17 14:59:42 +02:00
|
|
|
- Create an admin user during the container deployment
|
2020-10-07 16:42:24 +02:00
|
|
|
- should there be a datapusher container built? maybe an xloader container?
|
