johnyb / ffmap-rethinkdb Goto Github PK

This can then be used to support clients that can not handle websockets or prefer a REST API

for now, there should be a config.local.js file and the app script fails if this file is not available.

Workaround: cp config.js config.local.js

When connecting the frontend, it could provide a bounding box of the current view and the first batch of nodes could be those, that are within this bounding box.

There is ffmap-json-schema that can be used to validate the JSON sent to the client.

it should be possible to aggregate data from multiple sources. At the moment, only one element from the configuration is fetched.

There has been an article, lately that shows a really nice API to use rethinkdb. May be it's worth some refactoring.

it's not possible to import data from ffmap-backend#master … only dev-branch is supported at the moment. Most communities are still running master, so master should be supported, too.

Each community can provide a JSON file as specified by the Freifunk API. Those files can provide the endpoints and remotes for the nodes.json of the community as well as a filter (which would be an extension of the format) rule to help filtering nodes belonging to a community.

This enhancement would help smaller communities to share a single installation of ffmap for their users before splitting up, once a critical mass is reached.