Up to 4.0.9

.env

@@ -1,6 +1,6 @@
 TERRAMA2_PROJECT_NAME=terrama2
 TERRAMA2_DOCKER_REGISTRY=terrama2
-TERRAMA2_TAG=4.0.8
+TERRAMA2_TAG=4.0.9
 TERRAMA2_CONFIG_DIR=./conf
 TERRAMA2_DATA_DIR=data_vol
 TERRAMA2_WEBAPP_ADDRESS=127.0.0.1:36000

BUILD.md

@@ -31,15 +31,15 @@ After that, just run script **build-image.sh** to build:
 ## Publishing the Generated TerraMA² Images
 
 ```bash
-docker push terrama2/terrama2:4.0.3
+docker push terrama2/terrama2:4.0.9
 ```
 
 ```bash
-docker push terrama2/terrama2-webapp:4.0.3
+docker push terrama2/terrama2-webapp:4.0.9
 ```
 
 ```bash
-docker push terrama2/terrama2-webmonitor:4.0.3
+docker push terrama2/terrama2-webmonitor:4.0.9
 ```
 
 
@@ -52,4 +52,4 @@ If you want to query the registry, type the following URL in your browser:
 After all commands, try:
 ```bash
 docker image prune
-```
+```

README.md

@@ -180,7 +180,10 @@ Open NotePad with Adminiistrator and then modifify the file `C:\Windows\System32
 
 ### Services
 
-By default, the TerraMA² services are not started automatically inside container. In this way, we must configure these parameters in [`Web Application`](http://127.0.0.1:36000) to associate with respective container.
+We must configure service parameters in [`Web Application`](http://127.0.0.1:36000) 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`.
 
 
 ## Tips
@@ -189,4 +192,4 @@ Launching TerraMA² through docker-composer will name the containers with the su
 
 ```bash
 docker exec -it terrama2_webapp_1 bash
-```
+```