Closed bieganowski closed 2 years ago
I would compare and update the docke-compose.yml with the GeoNode master one.
Make sure to update it accordingly to the {{project_name}}
template.
@afabiani are you sure? The two are not only different in version and syntax but also between services definitions. For example geoserver image is built from the local docker definitions in geonode-projecg, while geonode uses the docker hub image.
What do you mean by using the one from geonode?
I mean, re-using the same approach and concept from docker compose 3.4
@afabiani, @giohappy docker-compose
file is updated in accordance to Geonode's master one. I conducted some simple tests (including creating a project based on this geonode-project's branch, setting up the environment with docker-compose, and loading a layer) and everything works fine, but it would be great, if you could take some time to check if there are no mistakes there.
From changes which might be interesting
django
image, I changed the health check address from 127.0.0.1:8000
to django:8000
, since only django
is by default allowed in ALLOWED_HOSTS
settingdjango
image, I extended the health check's start_period
to 120 seconds (from 60s), since during the test, the indicator showed the container to be unhealthy for a short period of time after healthcheck: starting
restart: unless-stopped
option, contrary to the geonode's file looks good
no syntax changes between the two versions @bieganowski?