Skip to content
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

Update git submodule #13

Closed
luwol03 opened this issue Nov 15, 2020 · 2 comments
Closed

Update git submodule #13

luwol03 opened this issue Nov 15, 2020 · 2 comments

Comments

@luwol03
Copy link

luwol03 commented Nov 15, 2020

Hello guys,

I found it very difficult to understand, how these repos are connected together. so I then made myself and made a simple diagram. in doing so, i came across the question, why don't you take your own anki sync server out of the organization. that made it very difficult for me to understand.

I suggest to update the git submodule to the organizations anki sync server.

Anki-Seite-2

@kuklinistvan
Copy link
Collaborator

Hello @luwol03,

For the record, I'm quoting you and @VikashKothary from Gitter:

can anyone explain to me why the structure of each server project is so complicated? i once set up a small diagram and wanted to ask two questions about it.
is what I have drawn so correct?
why does ankicommunity/docker-anki-sync-server not use ankicommunity/anki-sync-server but kuklinistvan/anki-sync-server ?

Hi @luwol03, that's a very good question. Here are my comments:

The first thing to note about why there are so many different versions of the applications. The main reason is that before this community, each project was maintained by separate individuals. As such, each individual project had different forks and different features. See this ticket for a brief history of where the projects came from: ankicommunity/ankicommunity-sync-server#33 (comment)

The second thing to note is that we're in the process of aligning and combining all these repos into a single stable collaborative project. You will see multiple issues regarding this across all the repos.

Now what does this mean for you. To provide any recommendations we'd need to understand your requirements however you mentioned production use so I'll riff on that a little.

Production usage has a lot more steps then picking between the two sync servers e.g. a scalable database architecture, load balancing, etc. But I'm assume what you are asking for is which is more stable for long term usage. I support @kuklinistvan's recommendations to use the anki-sync-server. This is simply because that is the project which has the more current users. I would even take it a step future that you open a ticket in the docker-anki-sync-server to update the docker image source to the anticommunity repo. It would add some considerable changes include bug fixes and new features.

That being said, your interest in migrating to the Django version is very valid. Again @kuklinistvan's recommendations are the best advice at this time. That being said, I want it to be clear that there will be a clear migration path for all those who want to adopt the newer project once it becomes the default.

@VikashKothary
Copy link
Member

This project no longer uses git submodules. It will download the latest release at the time of building.

I hope this resolves this issue. Feel free to open it again if there's anything I missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants