Ggrin's remotestorage-example-server

@ggrin wrote a remotestorage server which is published here: and here:

looks like a cool project! did anybody try it out yet?

@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 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

initalTokens: {
  me: {'token1': [':rw'],
       'token2': ['pictures:r']}
  you: {'token3': ['pictures:r','profile:rw']}

produces the user me and you, ‘me’ with two tokens for two diffrent scopes, and ‘you’ with one token granting access to pictures and profile.

the whole configuration process used in start.js is quite easy, have a look at config.js where comments and example values should guide you through available options.

I am not shure how the configuration of reStore works and how easy or hard it is to set it up, include it into another project.

Again, I mainly did this to be used in integration tests.

ok, so can you reply to my points



In other words, @ggrin, do you

  • want your work to be published?
  • like the idea to modularize it a little further towards remotestorage-server?

Is the HTTP behavior of a remoteStorage server compliant with any versions. I do have an old one, and hoping it could work with latest updates or versions.

I’m sorry if it’s not, but your entry looks a bit spammy. If it is an honest question, could you elaborate on what exactly you’d like to know it’s compliant with?