I will ask the devs about what does this exactly mean and will change it according to that.
The example is showing a simple case,
let’s say that you docker run -d -p 8080:8080 pydio/cells
on your machine, then you will only be able to access to it through https://localhost:8080
on the same machine that has the container running ( because of the external ) if you wanted to have access from another machine (for my example i will talk about local network) the best practice would be to have CELLS_EXTERNAL = the machine that has the container running) ip + port
, then you can access it from outside your own machine (right now i’m only talking on a local scale) but you can apply the same process with a server.
I never said it was the same, it will only work in the case that you are launching and accessing the container on the same machine ( but what would be the point of this, that was just an example ), sorry if was not clear but the host is the ip of the server/machine running the container.
I was just saying what method we also have, i also would have liked if my forum & site account were the same but i can understand your pain.
I myself did not really pay attention to this sentence about the ports, i mean i have a container running with exposed port 8080
then i would put the same port on both or alteast on CELLS_BIND
.
What is the case that requires you to have 2 different ports, (That’s why i asked if you are going to use Reverse proxy, but it could also be that you exposed a different port on your container)
Regards/