...
| Code Block |
|---|
127.0.0.1 sormas-docker-test.com
|
As the user running docker-compose create these directories:
| Code Block |
|---|
mkdir /srv/dockerdata/sormas/psqldata
mkdir /srv/dockerdata/sormas/sormas-backup
mkdir /srv/dockerdata/sormas/sormas-web
|
Downloading SORMAS in your system
...
| Code Block |
|---|
docker pull hzibraunschweig/sormas-application |
Running
...
SORMAS
Start the application
Check out this repository
Open a Shell in the projects project root directory (the directory containing the docker-compose.yml
Type in
...
DB_DUMP_MEM: Maximum available memory for the database dump tool.(For example 500M for 500MB) DB_DUMP_MEM_RESERVED: Memory reserved for the database dump tool. This memory may not be used by other processes on the same host. (For example 100M for 100MB) DB_DUMP_CPUS: CPU cores reserved for the used web server. This should be a floating point value. (Example: 0.5 )
PostgreSQL upgrade notes
The following tips are for people who use the project's Docker images to host a SORMAS (PostgreSQL) database in their deployment.
With the release of v2.50 the default database engine version will change, PostgreSQL 10.18 will be replaced with PostgreSQL 14.9
Before using this update, you must migrate the data structures of the current PostgreSQL instance yourself.
Bearing in mind that each deployment may be different, below are some steps on how to perform such an update (please bear in mind that these instructions will need to be adapted to individual deployment conditions).
You need to run a temporary container with PostgreSQL version 14.9 and indicate the local file system as the data storage location (please adjust the volume '/custom/mount' according to own environment)
| Code Block |
|---|
docker run --name postgres_149 -v /custom/mount:/var/lib/postgresql/data -e POSTGRES_PASSWORD=mysecretpassword -e DB_NAME=sormas -d postgres:14.9 |
Run a 'pg_dumpall' command, pipe the output to feed the psql command within new container (please adjust the name 'current_postgresql_instance' to the ones used withing own environment).
| Code Block |
|---|
docker exec -it current_postgresql_instance pg_dumpall -U postgres | docker exec -i postgres_149 psql -U postgres |
Stop the whole Docker application stack including temporary 'postgres_149' container
Secure the initial (current_postgresql_instance) data folder (copy / archive)
Copy the data related to postgres_149 volume as it was configured within current configuration of application stack
You can start the application stack and use new 'postgresql' images (please keep in mind, that the underlying data was changes and it's required from now to use news postgres image)