remoteStorage

Get storage : inventory March 2018

Hi,

By browsing the projects listed on the wiki page: https://wiki.remotestorage.io/Servers, it seems that the only operational solutions today are 5apps storage and php-remote-storage :

  • 5apps storage works well but it is a hosted solution

  • php-remote-storage remains a little complex to implement for a neophyte.

For the other solutions the inventory of fixtures seems to be this one:

  • Indie hosters makes no more mention of the remoteStorage protocol
  • mysteryshack is no longer maintained: https://github.com/untitaker/mysteryshack/issues/74
  • reStore hasn’t received an update for more than two years
  • rs-serve hasn’t received an update for more than 4 years and the debian package doesn’t seem to exist anymore
  • Cozy => the remoteStorage add-on is no longer available in the new version (cozy v3)
  • remoteStorage-server hasn’t received an update for more than 3 years
  • liquor cabinet isn’t really for the neophyte

What are the solutions commonly used in 2018 by remoteStorage protocol users ?

Thanks for your returns.

  • php-remote-storage is probably the best one for a newcomer, and it’s maintained by @fkooman who is a co-editor of the protocol draft.

    Could you elaborate why it seems too complex for a newcomer? It would help a lot with fixing that. Also, it’s open-source, so any contributions – even if it’s just opening an issue on GitHub – would help a lot.

  • mysteryshack works well in general (using it all the time for app development mself). Apparently @untitaker decided to stop maintaining it less than 24 hours ago. So it’s still well up-to-date, and as it is open-source, and based on modern Rust code, it’s easy for anyone with Rust knowledge to update it from there on.

  • restore is a bit of a difficult story, because unfortunately the original author doesn’t seem overly interested in coordinating any contribution efforts. @les has been maintaining a fork of it, with the last commit from September 2017, and I just noticed that someone else had also rewritten it in modern JS (according to the last commit message). Check out the network graph.

    It would probably make sense to update the wiki in regards to that information, especially because it looks like that last fork is not using @les’s improvements.

    However, in general that means restore seems to be alive and being worked on, but people are currently being directed to the unmaintained version, and it would be great if we could coordinate development efforts between the new contributors!

  • I don’t know about Indie Hosters really, but I think they were using restore, and afaik it would mostly be a matter of providing a Docker container with anything that works, in case we want them to provide RS again.

  • liquor-cabinet is actually the open-source RS API part of 5apps Storage, and in active use by tens of thousands of people every day (as the hosted version). It is actively maintained by the 5apps team, and we keep adding fixes and improvements all the time, based on edge cases we see in the wild. The reason it’s only the API part, and doesn’t contain signup/auth and Webfinger, is that it is meant to be added to existing systems and accounts. So yes, this one is not for end users who self-host, but for any providers who want to add RS to their users’ accounts.

  • I think the Cozy add-on was based on remoteStorage-server, which indeed is kind of dead. Same as rs-serve, which is also a very old project.

So, a the end of the day, for end users right now php-remote-storage and mysteryshack would be the best choices imo, with restore looking like we could coordinate to make it a legit choice as well.

Considering that the RS protocol spec is actually still a draft, it’s kind of a miracle that we already had so many different implementations being built by so many different authors. Most pre-RFC drafts are lucky to even have two different ones. And with usable implementations in all of PHP, Rust and JavaScript I think we’re in a great position for getting the protocol to a final state sometime soon. Go, people! Go, open source! :fist:


P.S.: I just opened an issue on the latest fork of restore, suggesting to coordinate efforts with @les and maybe create a new shared repo/org, where we can send users and developers.

P.P.S: We already got the ball rolling to move reStore to an org repo under a new name and make it a thing again.

Thanks basti for those detail response,

The installation of php-remote-storage seems not too much difficult but it requires some basic knownledge in an apache’s server installation and configuration. These aren’t been so simple for new comers and brings up a number of questions as : have I correctly configured data folder? have I installed all dependencies? Is the SSL certifcate installation realy right? Are my datas realy safe on my own server?

Solutions thats would rely on projects as nextcloud, cozy or yunohost would ease the life of new comers.
Let’s wait the next upcoming final state of the protocol!

Update:

The new reStore fork is called armadietto (Italian for “locker”), and you can find it here: https://github.com/remotestorage/armadietto

1 Like

It’s been a year; is armadietto is still the answer for an integration today?

Is it a toss between php-remote-storage and armadietto or is php-remote-storage a more bulletproof implementation?