#102 - Remove portmapping for elasticsearch and add proxy hint to readme

- Remove port mappings from dataportal-elastic service
- Add hint to proxy settings in readme

feasibility-portal/README.md

@@ -97,6 +97,8 @@ For the reverse proxy you need to choose the configuration (variable `FEASIBILIT
   - `uiBackendApi > baseUrl`: set the domain part of the local feasibility portal backend with the context path `/api`. For example https://example.org/api.
   -  `auth > baseUrl`: set the domain part of the local feasibility portal keycloak the context path `/auth`. For example https://example.org/auth.
 
+In case you do **not** have a docker-wide configuration of your organizations proxy server(s) you might need to add the following parameters to the `environment` section of the `init-elasticsearch` service in `backend/docker-compose.yml`: `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY`. The first two should obviously be your proxy server, the last one must include `dataportal-elastic`. 
+
 Please note that the keycloak provided here is an example setup, and we strongly recommend for each site to adjust the keycloak installation to their local security requirements or connect the local feasibility portal to a keycloak already provided at the site.
 
 For more details on the environment variables see the paragraph **Configurable environment variables** of this README.

feasibility-portal/backend/docker-compose.yml

@@ -108,9 +108,6 @@ services:
         target: /var/lib/postgresql/data
   dataportal-elastic:
     image: docker.elastic.co/elasticsearch/elasticsearch:8.16.0
-    ports:
-      - "127.0.0.1:9200:9200"
-      - "127.0.0.1:9300:9300"
     healthcheck:
       test: [ "CMD-SHELL", "curl --silent --fail localhost:9200/_cluster/health || exit 1" ]
       interval: 30s