Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gziping tiles #7

Open
lazydino opened this issue Jun 23, 2016 · 0 comments
Open

gziping tiles #7

lazydino opened this issue Jun 23, 2016 · 0 comments

Comments

@lazydino
Copy link

Hi,

It looks like I need to modify the GO server to do gzip for my custom tiles. I'd like to deploy the terrain server as it is via docker container as pulled from docker hub at https://hub.docker.com/r/geodata/cesium-terrain-server/ Any one know what should I do with my nginx reverse proxy setup so I can serve gzip terrain tiles for the my upstream Cesium Terrain Server?

I have my CTS container running at port 8088

docker run -d --name CTS -p 8088:8000 -v $TILEPATH:/data/tilesets/terrain geodata/cesium-terrain-server

and create a little nginx config

server {
listen [::]:80;
listen 80;
server_name myterrain.mydomain.net;

location / {

gzip on;
gzip_types    application/octect-stream;

proxy_pass  http://tiles;
proxy_http_version 1.1;

}
}

upstream tiles {
server 127.0.0.1:8088;
}


It is not working, but if I put a gizp respond filter on the go source code like https://github.com/NYTimes/gziphandler , and run it outside of docker work. Can anyone help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant