39467745f1
- Data only container for Postgres db & CKAN FileStore - Nginx container (still based on official container, but copies the config for portability) UPDATED: - Postgres Dockerfile to allow custom PGDATA directory & initiate it if it's not there or is empty - fig.ml to reflect the latest changes (datapusher, nginx, data container) |
||
---|---|---|
.. | ||
apache2 | ||
ckan | ||
cron.d | ||
my_init.d | ||
postfix | ||
supervisor/conf.d | ||
README.md |
README.md
_etc
This directory contains configuration files that are copied to /etc in the container when the Docker file is built, and when a child is built.
Customisation
- Apache config
- CKAN config
- You can specify custom options in the custom_options.ini file, they will be applied to the default ini file.
- or override the default (generated) config with a volume
- filenames (of the config & custom_options file) can be overriden with environment variables
- Cron jobs
- Postfix config
- Supervisor managed processes
Ngnix is not installed in the CKAN container anymore. Use the official Ngnix container, or a custom built container instead
- Nginx conf is stored in this folder for consistency.
- The default config uses "ckan" as a hostname, the corresponding IP address is resolved by linking the ckan container, which adds an entry in
/etc/hosts
inside the container. Make sure you link your CKAN container asmy_ckan:ckan
or change the config.
Usage
Building the CKAN image
i.e. This docker file
This will copy the files using the Docker ADD
instruction
Building a child image
i.e. A different Docker from the CKAN image (downstream build)
This will override the files using the Docker ONBUILD
instruction
This means that when building a child image, you should have the same directory structure.