Closed Castavo closed 3 weeks ago
I added a commit about the limited purpose of the docker compose deployment method
@ElysaSrc neat ! Then should I close the PR completely or keep it to add only the detail about the docker-compose deployment being a tad unsafe / not protection ready ?
@ElysaSrc neat ! Then should I close the PR completely or keep it to add only the detail about the docker-compose deployment being a tad unsafe / not protection ready ?
As you wish, adding a word about the docker compose deployment being unfit for production is a good idea.
I feel these changes are not required anymore since ROOT_URL is not used anymore : the gateway serves both on the same domain and the front uses a relative path
It shouldn't be, but it is... (editoast uses it to determine the url the layers are served from)
Dang So it's a bug ?
@ElysaSrc at least we can merge the warning
Discussed with @flomonster, ROOT_URL is still here because we can't give relative URLs to MapLibre... So it's probably here to stay
Yes since it's still in use you can merge the PR like it was the first time.
Sorry for the confusion.
I re-added the part about ROOT_URL @ElysaSrc
I'm pretty sure more changes are needed to deploy OSRD on the internet using docker-compose. The docker compose setup is designed for development only: no authentication is supported, the front-end is served in development mode (rebuilt on the fly).
I'm not comfortable suggesting this setup unless someone puts real effort into making it safe