pedros007 / mapserver-docker Goto Github PK

Hi all, this looks like a great project! I wanted to flag the below as I see you're calling s3://landsat-pds in your example.

https://lists.osgeo.org/pipermail/landsat-pds/2020-December/000178.html

I mean something like /{x}/{y}/{z}?

I'm wondering if such a thing is possible for Cloud Optimized GeoTiffs? I know there's also https://github.com/hotosm/oam-dynamic-tiler (which I'm helping with), but it doesn't support GeoTiffs as far as I know yet.

$ docker run --rm -it -p 8000:80 -v "/Users/comp/Documents/GitHub/raster-processing-demo/src/mapserver-tiles/mapfiles:/usr/src/mapfiles" mapserver-docker

/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2018-08-06 06:03:29,782 CRIT Supervisor running as root (no user in config file)
2018-08-06 06:03:29,782 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2018-08-06 06:03:29,788 INFO Creating socket unix:///var/run/mapserver.sock
2018-08-06 06:03:29,789 INFO Closing socket unix:///var/run/mapserver.sock
2018-08-06 06:03:29,801 INFO RPC interface 'supervisor' initialized
2018-08-06 06:03:29,801 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-08-06 06:03:29,801 INFO supervisord started with pid 9
2018-08-06 06:03:30,807 INFO spawned: 'nginx' with pid 12
2018-08-06 06:03:30,808 INFO Creating socket unix:///var/run/mapserver.sock
2018-08-06 06:03:30,810 INFO spawned: 'mapserver_02' with pid 13
2018-08-06 06:03:30,815 INFO spawned: 'mapserver_03' with pid 14
2018-08-06 06:03:30,818 INFO spawned: 'mapserver_00' with pid 15
2018-08-06 06:03:30,821 INFO spawned: 'mapserver_01' with pid 16
2018-08-06 06:03:30,823 INFO spawned: 'mapserver_06' with pid 17
2018-08-06 06:03:30,825 INFO spawned: 'mapserver_07' with pid 18
2018-08-06 06:03:30,830 INFO spawned: 'mapserver_04' with pid 19
2018-08-06 06:03:30,834 INFO spawned: 'mapserver_05' with pid 20
2018-08-06 06:03:30,880 INFO exited: nginx (exit status 1; not expected)
2018-08-06 06:03:31,884 INFO spawned: 'nginx' with pid 21
2018-08-06 06:03:31,884 INFO success: mapserver_02 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,885 INFO success: mapserver_03 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,885 INFO success: mapserver_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,885 INFO success: mapserver_01 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,885 INFO success: mapserver_06 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,886 INFO success: mapserver_07 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,886 INFO success: mapserver_04 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,886 INFO success: mapserver_05 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-06 06:03:31,900 INFO exited: nginx (exit status 1; not expected)
2018-08-06 06:03:33,907 INFO spawned: 'nginx' with pid 22
2018-08-06 06:03:33,921 INFO exited: nginx (exit status 1; not expected)
2018-08-06 06:03:36,931 INFO spawned: 'nginx' with pid 23
2018-08-06 06:03:36,946 INFO exited: nginx (exit status 1; not expected)
2018-08-06 06:03:37,927 INFO gave up: nginx entered FATAL state, too many start retries too quickly