https://github.com/mozilla-services/syncstorage-rs
It includes a Docker Compose setup.
Standard directory servers aren't specifically built for end-to-end encryption, while data in Firefox Sync is end-to-end encrypted by default. Firefox Sync must also scale to support the millions of Firefox users who use Mozilla's instance.
So the above (synstorage-rs_in_container) is now the only required software needed, and now includes the identity-server portion?
I would really like to use the "beam-a-tab-to-some-other-firefox", been a FF user since before it got that name. But i wanted to self-host all parts, and then found some info, that suggested, that 2 parts are needed: the SyncServer, the above open-source thing, and the Identity-server, on which i did not find much info at the time.
Do you have a link to recent-ish write-up of the current situation, that you can validate to be correct-ish?
Thanks again
Also, w.r.t Directory-Servers/Security: Enterprise printers have been able to authenticate Users with SSL/TLS-secured connection for more than a decade. So why not a "syncserver for URLs of open tabs per User"?
https://blog.mozilla.org/services/2020/09/15/the-future-of-s...
But, as you mentioned, the current documentation is here:
https://mozilla-services.readthedocs.io/en/latest/howtos/run...
You might also find the unofficial Arch User Repository package, comments, and PKGBUILD file helpful:
https://aur.archlinux.org/packages/firefox-syncstorage-git
I hope it works out for you!
https://mozilla.github.io/ecosystem-platform/tutorials/devel...
There's a lot of components directly hooked into Google Cloud that also make it difficult in terms of configuration. At some point I think creating an actual user's guide for this would be good for the community interested in self-hosting this on their own.