Open bdon opened 1 year ago
Here's a way to work around it for now:
go run main.go serve . --bucket=file:///full/path/to/folder
The "bucket" is a path like file://
or s3://
while the .
is the prefix within that bucket. Right now the way the local file paths work is consistent with remote buckets. We could add some sugar to detect the local-paths case to make it more intuitive?
This may be relevant: I have a directory
tiles
with a single archive,test.pmtiles
. Runningpmtiles serve . --cors=\*
from within that directory does allow me to access tiles atlocalhost:8080/test/z/x/y.mvt
.localhost:8080/test/metadata
also gives the expected response.However, running
pmtiles serve /full/path/to/tiles --cors=\*
results in the following error:Note that the full path to the
tiles
directory is repeated.localhost:8080/test/metadata
returns the responseArchive not found
.