Hi,

I'm a long time user of Firefox (and TB), and have been happily using
Weave and descendents for a long while mainly for synching my desktop
with my laptop. (My phone could appreciate that too)

I have managed to get a self hosted weave server up and running until
recently, and it seems current release of Fx needs fxacct (+...) to keep
synch running. So I'm trying to get a working infra to support current
synch services and dependencies.

So far, based on
https://mozilla-services.readthedocs.io/en/latest/howtos/run-fxa.html,
I've started to implement services with default configurations for sync,
fxa, db and content.
I've also read
https://blog.moomoocamp.net/index.php/firefox-sync-server-setup/ which
details steps to follow towards my goal, but may be old ?

So far, I managed to get sync, db, auth and content "up" but have not
been able to get Fx to "engage". Direct access to the content service
did create a user, but then logging from Fx results in a blank page and
an invalid connection try to a local oauth service ?

So here: Is there any current document that can be used to understand
the whole system enough to be able to deploy the supporting
infrastructure to get fx-synch working w/o relaying in Mozilla central
services ?
If not, tips to do it ?
If not, would it be ok to ask here may be dumb questions to get this
operational ? :)

TIA,
-Carlos

-- 
Carlos G Mendioroz  <[email protected]>  LW7 EQI  Argentina
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to