Firefox

17811 readers

10 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

[email protected]

GitHub - jeena/fxsync-docker (github.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

I had a hard time setting up the new sync server for Firefox which is written in Rust because the documentation is very bad.

After a lot of try and error and reading comments of people in the issue tracker I finally was able to set it up and run it successfully.

Mostly for my future self, but perhaps it also helps other people I documented it with help of a README and a docker-compose.yaml which makes it easy for me to upgrade if necessary and also to store all the other config files with examples.

top 7 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 1 year ago (1 children)

Oh, I'm using that... But I can run my own server for it,? That is 😎

[–] [email protected] 1 points 1 year ago

Yeah that was my main reason why I never switched to Chrome.

[–] [email protected] 1 points 1 year ago (1 children)

What is this server?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

It's a server to synchronize passwords, tabs, settings, etc. between the Firefox instances you use on different computers and devices.

[–] [email protected] 1 points 1 year ago (1 children)

So... the original docs are hard to read but its totally reasonable to run multiple MariaDB containers for a single thing that could be done with SQLite?

[–] [email protected] 3 points 1 year ago (1 children)

Nobody said it was reasonable. I didn't optimize anything, it probably could be slimmed down in some way.

The original software is written to be run on mozillas scale, they only bolted on the selfhosted solution on the side without any documentation. I'm happy that it's at least working, because I couldn't install the old version which is written in Python 2.7 on my server anyway anymore.

I have a 6 month old at home so I have half an hour here and there and it took me a couple of weeks to research deep in the comments of the issue tracker and make it work. So once it started working I quickly documented it mostly for my future self and then put it on github just to help others to shorten this research time.

I hope in the future at least the documentation part will be part of the original repo, but I'm not holding my breath that they will optimize anything for selfhosters. Once my son is in kindergarten perhaps I'll have more time over to look into replacing MariaDB with sqlite and upstream it.

[–] [email protected] 2 points 1 year ago

Thanks for your efforts, I guess going for a single MariaDB instance would be great as it uses a LOT of resources. SQLite was kind of one of those nice things that are what they are.