Running t_rex from within a Docker container cannot connect about t-rex

[pka]

Makes absolutely sense, but I could swear it worked for me...

[hunt3ri]

I'm completely prepared to believe I've made an elementary mistake. However, I tried a few things with no success.

A config switch on the next release to specify the socket would be awesome. Gunicorn calls the switch bind, and uwsgi http-socket. Perhaps http-socket is the most descriptive. Something like:

t_rex serve --dbconn postgresql://postgres:password@postgis/data-loader --http-socket 0.0.0.0:6767

[pka]

You can configure the bind adress, but currently only in the configuration file: http://t-rex.tileserver.ch/doc/configuration/
It makes absolutely sense to expose this as a command line parameter.

[hunt3ri]

Ahhhhhhh I didn't see that config option right at the bottom of the config file 😄

Tweaked it and now happily running t_rex from within docker. It would be handy having it as a cli param though.

Thanks for the quick response.

[pka]

CLI options bind and port are added now and a Docker image is published.

Usage example:

docker pull sourcepole/t-rex
docker run -p 6767:6767 -v $(pwd):/var/data/in sourcepole/t-rex serve --bind=0.0.0.0 --openbrowser=false --datasource=t-rex-gdal/natural_earth.gpkg

[hunt3ri]

Thanks for implementing this, appreciated 👍