- cross-posted to:
- selfhosted@lemmy.world
- linux@lemmy.world
- firefox@lemmy.ml
- cross-posted to:
- selfhosted@lemmy.world
- linux@lemmy.world
- firefox@lemmy.ml
This repository is holding a working docker-compose setup for documentation pourpuses because syncstorage-rs’s documentation is not very good to explain how to self host the new rust syncserver.
With help of it you can self host the new Firefox sync server, which is written in Rust and replaces the old python one, which is deprecated.
Why does this need 3 mariadb containers?
Well four is just a bit absurd
Five is right out
Probably because it was built to support hundreds of thousands of users, versus the arguably unusual self-hosted single user instance.
Because its Docker crap ahah
Here is the thing: in the last few years I came to the conclusion that if a tool isn’t simple enough to install and configure manually with one or two files it isn’t worth my time.
docker-compose.yml is only one file.
Checkmate.
Ahaha very good. One file to launch all kinds of hell.
Yeah the need for 3 mariadb containers is ridiculous.
Ask the author of the GitHub repo. He made the original !firefox@lemmy.ml submission and will get a notification when you ask there.
One is just running a command and exiting. They seem to be using a separate container for sync storage and token storage. Not sure what those are but is likely set up this way for scaling. This could probably be pretty easily worked in to one container with a start up script that runs that SQL command. The overhead of running multiple Mariadb containers isn’t that much though so it probably doesn’t matter much.
At first I thought why not just SQLite instead of a mariaDB, because as a self hoster you’ll probably have max 10 users on it anyway, is there a benefit to use mariaDB? Then noticed it’s not 1 but 3 seperate DBs ¯\_(ツ)_/¯