Replies: 2 comments 7 replies
-
@mholt it works now! I haven't updated it for at least a year or two - I think what I traced was an issue in the Go standard HTTP library that was taking a huge amount of time inside the HTTP Byte Serving implementation (not related to Caddy code itself), but I recently stood up a new server using Caddy and it seems to not be an issue anymore. Updating it now to:
BTW, I'm going to publish some docs for "serverful" deployment soon and I'll recommend running Caddy as a reverse proxy in front of https://github.com/protomaps/go-pmtiles. This is for serving ZXY tile endpoints and not byte ranges, which can be faster and more compatible with frontends. I think letting Caddy own SSL termination and header configuration is much better than reproducing all of that in go-pmtiles code - is there an advantage to writing a module instead? |
Beta Was this translation helpful? Give feedback.
-
@bdon Ah, excellent!! Thanks for checking again. I'm a big fan of the Protomaps project after just learning about it last week.
Yeah, absolutely -- if go-pmtiles has an HTTP handler, you could easily turn that into a Caddy module with a few lines of boilerplate you can copy paste from our Extending Caddy docs. |
Beta Was this translation helpful? Give feedback.
-
The Protomaps docs say:
Can you elaborate?
Beta Was this translation helpful? Give feedback.
All reactions