Francesco Frassinelli
Francesco Frassinelli
Never :)
`GEONODE_LB_PORT=` should be changed too to match the new port. I noticed another issue after that: the home page cannot load properly, as shown in this call: ``` GET http://localhost:5080/proxy/?url=http://localhost/api/v2/resources?page=1&page_size=20&filter%7Bmetadata_only%7D=false&include=executions...
Reproducible on master.
Problem still affecting geonode-project 3.2.x.
Ok, I think that this is due to how Docker handles volumes differently from directory. In this case, Docker copies the files over the volume, while a regular mount overrides...
@gannebamm `data-dir-conf` relies on a very specific behaviour of Docker, which is obscure and hard to figure out by just looking at the compose file; this is why it should...
They should be printed to stdout and stderr by default, in my opinion. `INVOKE_LOG_STDOUT` is a step in the right direction, but we do not have an equivalent for `geonode.log`.
This is also problematic in case there is a network firewall with an anti-spoofing mechanism. Communication between GeoNode components should always happen using internal hostnames.
`GEOSERVER_WEB_UI_LOCATION` and `GEOSERVER_PUBLIC_LOCATION` should use HTTPS (the last one especially). Be sure to not having set `HTTPS_*` variables.
I got that, and I have the very same setup in my company. There is still need to know the public location of your service. `GEOSERVER_WEB_UI_LOCATION` is used for the...