The library is well-tested and actively maintained. It is safe to use in production.
Where to get help?
- See remotestorage.io for general information about the remoteStorage protocol
- Read the docs (source files in
- Ask questions on the community forums
- Ask questions on IRC in #remotestorage on Freenode (wait a bit, if nobody's responding right away)
- If you found a potential bug, or want to propose a change, open an issue on GitHub. New issues will usually receive a response within 24-48 hours.
Running a local test server
To develop remoteStorage-enabled apps, you need to have a remoteStorage-compatible storage account. We recommend php-remote-storage (PHP) or mysteryshack (Rust) for running a local test server, or for self-hosting an RS server.
You can also get an account with a hoster, or use one of the various other remoteStorage server implementations: Servers.
remoteStorage.js is a grassroots project, developed by the community, for the community. We'd be happy to count you among the many people who contributed to the project so far!
Read our Contributing docs to get started.
We adhere to Semantic Versioning. This means that
breaking changes will result in a new major version. With npm, you can make
sure to only automatically upgrade to API-compatible versions by using either
^ prefix, or
x as indicator for flexible numbers:
"devDependencies":"remotestoragejs": "1.x" // same as "^1.0.0"
Original authors: Niklas Cathor, Michiel de Jong
Sponsored by NLnet