git clone https://github.com/terrama2/docker.git
cd docker
conf
- Folder with all the configuration files of TerraMA² webapp and monitor;geoserver
- Dockerfile to build the Geoserver image;satalertas
- Dockerfiles anddocker-compose-yml
for the SatAlertas application;terrama2
- Dockerfile and scripts to build the terrama2 image;webapp
- Dockerfile to build the webapp image;webmonitor
- Dockerfile to build the webmonitor image.
backup.sh
- Saves a backup of the Geoserver, database and SatAlertas documents on the folder configured on the.env
file;build-images.sh
- Build the images for TerraMA² project;build-images-satalertas.sh
- Build the images for SatAlertas project;configure.sh
- Generates the TerraMA² configuration files (runningconfigure-version.sh
script) and containers, including the Geoserver;configure-version.sh
- Generate configuration files of the projects,Dockerfiles
anddocker-compose.yml
files using the.env
variables;create-postgres.sh
- Generates PostgreSQL container;deploy-terrama2.sh
- Updates TerraMA² images;deploy-satalertas.sh
- Updates SatAlertas images;push-satalertas.sh
- Pushes the SatAlertas images to the DockerHub;push-terrama2.sh
- Pushes the TerraMA² images to the DockerHub;restore.sh
- Restores the backup generated with thebackup.sh
script.
The .env
file contains configurable variables used on all scripts and docker-compose.yml
files. There's an .env.example
file on the root folder with the default variable values.
TERRAMA2_PROJECT_NAME
- Name of the project used on Docker Compose project (-p
) parameter;TERRAMA2_DOCKER_REGISTRY
- Name of the registry on Docker Hub;TERRAMA2_TAG
- TerraMA² version;SATALERTAS_TAG
- SatAlertas version;TERRAMA2_CONFIG_DIR
- Path of the config folder (located on./conf
);TERRAMA2_DATA_DIR
- Name of the data volume;TERRAMA2_WEBAPP_ADDRESS
- Host and port to access the webapp container;TERRAMA2_WEBMONITOR_ADDRESS
- Host and port to access the webmonitor container;TERRAMA2_GEOSERVER_ADDRESS
- Host and port to access the geoserver container;SATALERTAS_CLIENT_PORT
- Port to access the SatAlertas client container;SATALERTAS_SERVER_PORT
- Port to access the SatAlertas server container;TERRAMA2_DNS
- DNS of the server including protocol;TERRAMA2_BASE_PATH
- Base URL of the application included after the DNS (default is '/');POSTGRES_DATABASE
- Name of the database;BACKUP_DIR
- Directory used to store backup files;PUBLIC_URI
- Server DNS including the protocol (HTTP or HTTPS);WEBMONITOR_BASE_PATH
- Webmonitor base path;WEBAPP_BASE_PATH
- Webapp base path.
Just configure .env
file if necessary and run:
./configure.sh
To build postgresql container, run:
./create-postgres.sh
If you want to manually configure, follow the next steps.
Create a volume terrama2_shared_vol
:
docker volume create terrama2_shared_vol
If you don't have a running version of GeoServer or you want to try an experimental version, you can use the built-in TerraMA² GeoServer image.
Create a new volume to store the GeoServer data files:
docker volume create terrama2_geoserver_vol
Pull the GeoServer image and run a new container named terrama2_geoserver
:
docker run -d \
--restart unless-stopped --name terrama2_geoserver \
-p 127.0.0.1:8080:8080 \
-e "GEOSERVER_URL=/geoserver" \
-e "GEOSERVER_DATA_DIR=/opt/geoserver/data_dir" \
-v terrama2_data_vol:/data \
-v terrama2_shared_vol:/shared-data \
-v terrama2_geoserver_vol:/opt/geoserver/data_dir \
-v ${PWD}/conf/terrama2_geoserver_setenv.sh:/usr/local/tomcat/bin/setenv.sh \
terrama2/geoserver:2.12
The above command will link the host address 127.0.0.1
on port 8080
to the container port 8080
and it will run the container as a daemon in background. You can try the following address in your browser: http://localhost:8080/geoserver.
If you don't have a running version of PostgreSQL with the PostGIS extension or you want to try an experimental version, you can use the image prepared by mdillon/postgis
.
Create a new volume to store the PostgreSQL data files:
docker volume create terrama2_pg_vol
Pull the PostgreSQL image and run a new container named terrama2_pg
:
docker run -d \
--restart unless-stopped --name terrama2_pg \
-p 127.0.0.1:5433:5432 \
-v terrama2_pg_vol:/var/lib/postgresql/data \
-e POSTGRES_PASSWORD=mysecretpassword \
mdillon/postgis
The above command will link the host address 127.0.0.1
on port 5433
to the container port 5432
and it will run the container as a daemon in background. You can try the following address in psql or pgAdmin:
psql -U postgres -p 5433 -h localhost -d postgres
In the above command use the password: mysecretpassword
.
In order to link all the pieces of TerraMA², you can create a network named terrama2_net
:
docker network create terrama2_net
If you have installed the GeoServer and PostgreSQL as docker containers, as explained in above sections, link them together:
docker network connect terrama2_net terrama2_geoserver
docker network connect terrama2_net terrama2_pg
Edit the file conf/terrama2_webapp_db.json
with database credentials.
After that, configure files version properly:
./configure-version.sh
This command will generate conf/terrama2_webapp.json file. You may edit this file for connection parameters.
Now run the docker-compose in daemon mode:
docker-compose -p terrama2 up -d
If you want to check TerraMA² log output:
docker-compose -p terrama2 logs --follow
If you want to stop the TerraMA² containers:
docker-compose -p terrama2 stop
If you want to remove all the stopped containers:
docker-compose -p terrama2 rm
You can proceed to next post installation steps in link
.
Create a new volume to store the BDQueimadas Light temporary download files:
docker volume create terrama2_bdq_vol
Pull the BDQueimadas Light image and run a new container named terrama2_bdqlight
:
docker run -d \
--restart unless-stopped --name terrama2_bdq \
-p 127.0.0.1:39000:39000 \
-v ${PWD}/conf/bdqueimadas-light/conf/:/opt/bdqueimadas-light/configurations/ \
-v ${PWD}/conf/bdqueimadas-light/.pgpass:/root/.pgpass \
-v terrama2_bdq_vol:/opt/bdqueimadas-light/tmp \
terrama2/bdqlight:1.0.0
Link the BDqueimadas container in terrama2_net
:
docker network connect terrama2_net terrama2_bdq
To configure SatAlertas, navigate to satalertas
folder and run:
docker-compose -p terrama2 up -d
The docker-composer.yml
file uses the .env
file, so, it's necessary to run ./configure-version.sh
script.
On unix environment, add in the file /etc/hosts
with following statements:
127.0.0.1 terrama2_geoserver
127.0.0.1 terrama2_webapp_1
127.0.0.1 terrama2_webmonitor_1
Open NotePad with Adminiistrator and then modifify the file C:\Windows\System32\Drivers\etc\hosts
:
127.0.0.1 terrama2_geoserver
127.0.0.1 terrama2_webapp_1
127.0.0.1 terrama2_webmonitor_1
We must configure service parameters in Web Application
to associate with respective container.
On service hosts, unmark the option Local Service
and then set the respective container name to the service at Host Address
. For example, in the service Local Collector
, use address terrama2_collector_1
. For Local Analysis
, use terrama2_analysis_1
and so on.
When registering Local View
, make sure that you have configured the directive provided on section Run TerraMA² localhost
and specify the Maps Server URL
with terrama2_geoserver
.
Launching TerraMA² through docker-composer will name the containers with the suffix _1
. You can connect to the docker container with:
docker exec -it terrama2_webapp_1 bash