Altenatively, you could set up Webfinger manually. It’s the entry that tells a remoteStorage client where to find the authorization and storage endpoints for a certain user address. This is for example what my Webfinger entry for basti@5apps.com looks like:
https://client.webfinger.net/lookup?resource=basti%405apps.com
So in theory you can just publish an entry like that on your server using the official Webfinger URI format:
https://my-host.com/.well-known/webfinger?resource=acct:my-username@my-host.com
(See http://slides.kip.pe/remotestorage-intro/#slide-49 e.g.)
Edit: I’d agree that reStore is the most approachable server solution at the moment, though. It depends heavily on your technical experience, if you want to set up a server that requires you to solve some things manually. That’s usually the case with server libraries that are written to be integrated in larger setups and with existing user databases.