docker-ckan

Go to file

Brett e90088a183 Update README.txt		2020-10-07 16:42:24 +02:00
ckan	Another Update	2020-09-29 12:34:56 +02:00
datapusher	More commits	2020-09-29 16:56:10 +02:00
images	Another Update	2020-09-29 12:34:56 +02:00
nginx	First update (again)	2020-09-17 11:42:27 +02:00
postgresql	First update (again)	2020-09-17 11:42:27 +02:00
solr	First update (again)	2020-09-17 11:42:27 +02:00
.env	more updates	2020-09-17 14:02:02 +02:00
.env.template	Replace ckan-docker with the replacement (initial stage)	2020-09-17 11:32:00 +02:00
.gitignore	Initial commit	2014-10-26 21:21:58 +00:00
.travis.yml	Update .travis.yml	2020-10-05 14:32:08 +02:00
README.txt	Update README.txt	2020-10-07 16:42:24 +02:00
dev-requirements.txt	More updates	2020-09-17 14:10:25 +02:00
docker-compose.dev.yml	More updates	2020-09-17 14:10:25 +02:00
docker-compose.yml	Another Update	2020-09-29 12:34:56 +02:00

README.txt

### Please note that this re-purposed CKAN Docker repo is a WORK IN PROGRESS ###
### 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
- Create/access a CKAN datapusher image rather than build one?
- 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
- include an "/examples" folder for examples of adding extentions xloader, harvester, etc

- make sure the "development mode" path is taken cared of with any changes
- Create an admin user during the container deployment
- should there be a datapusher container built? maybe an xloader container?