Migrating from the Python syncserver

[bcspragu]

I've been running the Python syncserver (https://github.com/mozilla-services/syncserver?tab=readme-ov-file) for years and years, and it's probably about time I migrate to this version. I was mostly holding out on either Postgres (which I'm already running) or SQLite support, and it looks like Postgres is functional at this point, so why not.

My question is mostly around how to migrate all of my years of history. Is it as simple as pointing my browsers at the new endpoint, and they'll populate everything? I'm mostly just trying to avoid losing data or corrupting everything.

I didn't see any docs on the migration on the Python doc site, and I don't see many docs for the new server, is there a well-established process (or even just guidelines) on how to do this?

[felfert]

You don't, it happens automatically. All data on the server is also kept on the client(s).

This is what happens, if you reconfigure your FF to use a new server that has an empty database: On first connect, a big sync will happen, pushing ALL data to the server. This will probably take some time and that is the only impact.

There is a guide which I used to inspire me here, but this does not talk about postgres (yet?). I personally prefer MariaDB. Why? Because it is already on my LAMP stack.

Regarding maturity of the postgres variant:
As of this writing, I still would wait a little bit, perhaps until the latest bugs have been ironed out and they have made a new release here.

Cheers
-Fritz

PS: I have packaged 0.21.1 (mysql-only) with a few patches for Fedora, RHEL and Ubuntu 24.04 LTS and have started creating patched docker images as well. See here. As soon as I deem the postgres stable enough, I will offer packaged postgres variants as well.

[bcspragu]

Thanks for the info! I can't convince myself to self-host both MySQL/MariaDB + Postgres, so I'll wait a bit for Postgres to mature (or take a look myself, I had made a few small patches to the SQLite attempt before)