@ggrin i guess the goal is for it to be something in between the starter-kit and reStore? can you say some more about that, is it easier to configure than reStore?

i'm opening this thread here so that it's easier to find, but i think it should also be added on http://remotestorage.io/get/ and published on the unhosted mailing list.

also, it would be good to replace the remotestorage-server.js file in the source tree with require('remotestorage-server'), that way starter-kit, remotestorage-example-server, and (soon, hopefully) reStore all use the same "engine".

Yes, the remotestorage-example-server here is based on the code of the starter-kit but needed to be a standalone node package to be useful for integration-tests. The starter-kit was based on the remotestorage-example-server that was formerly part of the remotestorage.js repository and located in the server directory.

But it has, as it is now, no persistent storage abilities.

In the process of striping away functionality that wasn't needed to be an example-server(like hosting web-apps) some things changed a little. But the core part like remotestorage-server and webfinger-server are very similar to the starter-kit.

It is now possible to have seperate protocol, port, host and ssl values for each of the server parts(remotestorage, webfinger, oauth).

The pre-configuration of users/tokens works now in a way that we can have initial tokens for users with scopes. Meaning

i'm opening this thread here so that it's easier to find, but i think it should also be added on http://remotestorage.io/get/ and published on the unhosted mailing list.

and

michielbdejong:

also, it would be good to replace the remotestorage-server.js file in the source tree with require('remotestorage-server'), that way starter-kit, remotestorage-example-server, and (soon, hopefully) reStore all use the same "engine".