2024-10-09 15:06:56 +02:00
..
2024-10-09 15:06:56 +02:00
2024-10-09 15:06:56 +02:00
2024-10-09 15:06:56 +02:00
2024-10-09 15:06:56 +02:00
2024-10-09 15:06:56 +02:00
2024-10-09 15:06:56 +02:00
2024-10-09 15:06:56 +02:00

#########################################
#
# README
#
#########################################

Docker configuration : 

A docker-compose file bind 4 different docker-files to work together : 
- cstl-data : A shared volume. Designed to contain all data from Constellation-SDI and its admin database (BACKUP).
- FTP :  An FTP service to publish reference files and results Its data can be mounted from host by editing docker-compose configuration.
- db : PostgreSQL service to use with Constellation.
- Constellation : WFS service for geographic references.


Volume management : 

It is possible to use volumes on cstl-data and ftp container, to mount constellation / ftp data from host. By decommenting volumes section from the docker-compose file, and changing the left part (host) by the path on your host you want to use, you can make data independant from containers.

/!\ For the ftp volumes, you should be cautious about right management. If you want to make some directories/files read-only for the FTP user, you have to ensure that your owner on host has a different UID from the one in the docker file. If user UIDs are the same, your host files will be considered as owned by the container ftp user. To fully configure user mapping between host and container, you may want to look about user namespace feature.