CatalogueRevamping
/
docker-ckan
14
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.txt

This commit is contained in:
Brett 2020-10-07 16:42:24 +02:00
parent e2f467af48
commit e90088a183
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.txt
View File

@ -8,9 +8,11 @@ Potential ideas/investigations from Keitaro (Marko Bocevski) : https://github.co
located at the root directory located at the root directory
- Should we use wheels too? - Should we use wheels too?
- 2 networks: 1) Frontend 2) Backend - 2 networks: 1) Frontend 2) Backend
- Create/access a CKAN datapusher image rather than use keitaro/base:0.4 - Create/access a CKAN datapusher image rather than build one?
- all username/passwords as environment variables rather than hardcoded - 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 - "/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 - 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 - make sure the "development mode" path is taken cared of with any changes
- Create an admin user during the container deployment - Create an admin user during the container deployment
- should there be a datapusher container built? maybe an xloader container?