RDMO not reachable if via Docker host IP or if Docker host's hostname is not "rdmo" about rdmo-docker-compose HOT 2 CLOSED

Thanks for the compliments.

The issue described is something we need to think about. My first impression is being a little unsure about how I could contribute to fix the problem. The ALLOWED_HOSTS setting is a part of Django and serving security matters. As it would not be a good idea to remove it or use a wildcard to allow everything, we might need to think about what to add to the list to make the setup a little easier. Basically there are two options which unfortunately immediately lead to two problems which boil down to the question what to add to the list.

1. IP address: The docker containers do not have static IP addresses. Their IPs might differ from host to host. So what to add? Of course I could assign static IPs but I do not consider this being a good option because it could lead to address range clashes depending on docker host setups.
2. Hostname: I am unable to anticipate the hostname an RDMO docker setup might be using which is why I couldn't know what to add.

The best idea I have at the moment is to write a remark into the readme.md that the local.py needs to be adjusted to the specific needs. I suppose my misjudgement was taking this for being clear because it is mentioned in the RDMO documentation.

Or do you have any better idea?

from rdmo-docker-compose.

I decided to move the ALLOWED_HOSTS setting into the variables.env to raise awareness that there is something the needs to be adjusted. Therefore I consider this ticket being ready to be closed.

from rdmo-docker-compose.