You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While nodetiles-init serves as a simple example server and we have some simple Connect middleware in nodetiles-core, would it be worthwhile to have a project for building a more robust tile server with caching, render clustering, etc?
Not sure. Maybe something we should just let others tackle for now, too.
The text was updated successfully, but these errors were encountered:
Probably :-) I'm thinking of redoing nodetiles-init and just changing it to nodetiles-example. As always, I want to keep nodetiles-core as lightweight as possible.
I think the naming convention of "nodetiles-init" and "nodetiles-core" is very confusing.
The main project should be called "nodetiles" and everything else should have a suffix. Example:
-nodetiles
|--- nodetiles-example
|--- nodetiles-server
|--- nodetiles-datasources (since there is talk about breaking apart pg)
or even break down datasources even further:
|--- nodetiles-pg
|--- nodetiles-geojson
This was actually the original intention (hence the names!). The main project was just never made, since we all ran short of time after getting this together for NACIS.
While nodetiles-init serves as a simple example server and we have some simple Connect middleware in nodetiles-core, would it be worthwhile to have a project for building a more robust tile server with caching, render clustering, etc?
Not sure. Maybe something we should just let others tackle for now, too.
The text was updated successfully, but these errors were encountered: