gitea/ckan
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update README

Browse Source
This commit is contained in:
Brett 2022-07-20 12:47:36 +02:00
parent 647e930b08
commit 7381102495
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -141,14 +141,13 @@ ckan
## pdb ## pdb
Add these lines to the Dockerfile.dev
Debug with pdb (example) - Interact with `docker attach $(docker container ls -qf name=ckan)` Debug with pdb (example) - Interact with `docker attach $(docker container ls -qf name=ckan)`
command: `python -m pdb /usr/lib/ckan/venv/bin/ckan --config /srv/app/ckan.ini run --host 0.0.0.0 --passthrough-errors` command: `python -m pdb /usr/lib/ckan/venv/bin/ckan --config /srv/app/ckan.ini run --host 0.0.0.0 --passthrough-errors`
tty: true
stdin_open: true
## Known Issues ## Known Issues
* Running the tests: Running the tests for CKAN or an extension inside the container will delete your current database. We need to patch CKAN core in our image to work around that. * Running the tests: Running the tests for CKAN or an extension inside the container will delete your current database. We need to patch CKAN core in our image to work around that.

2
TODO.livelog.txt
View File

@ -25,7 +25,7 @@ NB: Had to update the prerun.py script as it was failing on check_solr_connecti
### ToDo (remaining things to think about and/or 'to fix') ### ### ToDo (remaining things to think about and/or 'to fix') ###
1. nginx - what caching should I implement? 1. nginx - what caching should I implement?
2. DataPusher - needed to use a custom requirements.txt (see https://github.com/ckan/datapusher/pull/251) 2. DataPusher - needed to use a custom requirements.txt as the official didn't work (see https://github.com/ckan/datapusher/pull/251)
3. Use Multi-Stage images defined in Dockerfile - get the CKAN images down to bare-bones...for security reasons really 3. Use Multi-Stage images defined in Dockerfile - get the CKAN images down to bare-bones...for security reasons really
Also check out https://github.com/ckan/ckan/pull/4635 for Francesco's test stuff Also check out https://github.com/ckan/ckan/pull/4635 for Francesco's test stuff
4. CKAN Worker (maybe) 4. CKAN Worker (maybe)

1
docker-compose.yml
View File

@ -38,6 +38,7 @@ services:
condition: service_healthy condition: service_healthy
ports: ports:
- "0.0.0.0:${CKAN_PORT}:5000" - "0.0.0.0:${CKAN_PORT}:5000"
volumes: volumes:
- ckan_config:/etc/ckan - ckan_config:/etc/ckan
- ckan_home:/usr/lib/ckan - ckan_home:/usr/lib/ckan