Conversation
Removing the use of a shared path aligns better with multi-provider support. Tile paths have a fully qualified path, remove use of relative path.
This is appended to the url path to the mapbox style json file.
Ensure operation behind proxy is not impacted.
Ensure operation behind proxy is not impacted.
panaaj
changed the title
|
@tkurki Can you please review and if all is OK it's good to publish. This code seemed to solve Freeboard-SK issue SignalK/freeboard-sk#211 |
README.md
Outdated
|
|
||
| Supports both v1 and v2 Signal K resources api paths. | ||
| Chart metadata is derived from the following supported chart files: | ||
| - Mapbox Tiles _(.mbtiles)_ |
There was a problem hiding this comment.
Afaik MBTiles is better known as just MBTiles and touted as open format. The spec README never mentions Mapbox, while it is under their Github org.
We could link to the canonical resources?
There was a problem hiding this comment.
Updated to MBTiles.
Which canonical resources are you refferring to?
|
Unrelated to this PR: README is not very consistent
|
|
I arrived here because I would like to have two things: 1. the file watcher, and 2. support for recursive folders. For a new region, I have to create the folder on the share, add it to the plugin, and restart for every chart I add. This PR implements the watcher. WDYT about letting the user specify recursive paths? |
panaaj
changed the title
|
This would need rebasing and a bit of work to address my comment about the docs. |
3 participants
This PR adds a file watcher to charts folders to detect new files placed in the folder. This makes the new charts available to subsequent requests without having to restart the plugin (#28).