-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How on earth to set this up on Docker in 2023 #1483
Comments
Hi, so we're a very small team split between several projects. Our main focus is, of course, providing a quality production product for firefox customers. This means that we have to provide a highly scalable system for our primary customers. Offering a configuration that can be run on private servers is something that we offered, particularly when we had load that could run on a suite of MySQL clients. That's kind of no longer the case. We will do our best to try and support the community, but we need the communities help for that. If there are things that would make your life easier, please do not hesitate to submit a PR. (Check with the CONTRIBUTING.md doc to make that smoother.) Thanks, as always for helping make things better for everyone. |
Have also a look on this thread: |
I crated this from my research for now https://github.com/jeena/fxsync-docker |
Repo only publishes the |
And why the sudden change? 0.13.7 worked with MySQL/MariaDB. How do I have to change my existing configuration to work with spanner? On the other side, I use selfhosting to get rid of external cloud services, and if I'm not mistaken, Spanner is a Google Cloud service... Hallelujah... |
Someone overlooked it? I proposed a fix here: #1496 |
You're right, I've overseen this totally, but I would second your proposal... |
docker-compose
(python script) is long deprecated replaced by in builtdocker compose
Instructions extremely unclear, gaps, referencing old and new GitHubs at the same time, "latest" image on Docker Hub actually ancient ... the list goes on?┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: