Document self hosting use case

[pjenvey]

Let's ensure there's documentation in place for self hosters.

Our README may already cover most of what they need: let's double check if there's anything to add. It should be roughly equivalent to syncserver's docs.

[Nadrieril]

Yay! Does that mean that this is starting to be usable as a replacement of the old Python syncserver?
EDIT: for other people excited about self-hosting, I found a meta issue for that: #550

[jrconlin]

That is one of the goals, yes. We had to focus on getting the Spanner data service working correctly so we could transition, but now are working to get the self-hosting side operational.

[fzzzy]

Should we instead update syncserver to bundle syncstorage-rs, and update those docs?

[jrconlin]

In the long term, I think updating syncserver would probably be best. I'm also somewhat in favor of keeping a well documented Dockerfile that shows the various elements and configuration steps that need to be done to get a locally hosted syncserver running. (Not everyone can or wants to run Docker, but a Dockerfile can act as a roadmap for setting things up.)

[piegamesde]

What's the state of this as of now? The issue was marked as Done and Archived some time ago.

[fzzzy]

There was some work done, but let's leave it open as there is more to be done.

[thomasdn]

I would really love to use Firefox Sync. But I don't want all my browsing history stored in a single place on someone else's computer.
I have not been able to find any official up-to-date docs on it. The Github README says that it is no longer maintained: https://github.com/mozilla-services/syncserver

As I understand this thread, it seems that self-hosted Firefox Sync is NOT currently supported.
Related: #550

Does this mean that all existing self-hosted FF Sync deployments based on the old guide are unsupported and likely highly insecure?

[retropele]

Could this be moved from "done" and "archived" into a current issue, as self-hosted sync setups are not currently viable in a secure and documented way? It is still noted across various docs that self hosting is possible, which isn't really fair when it seems it does not really seem to be.

Edit: I can see it is is possible, just not documented, so maybe that could just be noted (otherwise people might use the more insecure older implementation)? Not trying to be rude to a small hardworking team, it's just been 3 years and a hard answer from the get-go on what's out there and what's possible would be cool