You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This wiki uses dulwich which is a python git implementation, not libgit2 bindings like PyGit2. I can adapt the site to use either library I'm sure, but I don't believe either one support different backends besides filesystem and memory.
Solving this will enable this to become a 12-factor app, but I don't know how to do it.
The text was updated successfully, but these errors were encountered:
Would love to help here, but don't really see what you're getting at. I feel your choice of Dulwich is an excellent one, making this wiki easier to deploy, providing an accessible API for feature dev, and allowing for debugging with compatible code.
There is a blog post (blog.deveo.com) talking about pluggable backends where they write "Using alternative Git storage solutions is probably most interesting for services or products that provide Git hosting". Is realms-wiki really hosting Git? I don't see how one file at a time multi-user access really needs the performance boost, but I could be wrong.
Could you list any specific benefits you think PyGit2 would bring to development, as opposed to just the architectural elegance of a consistent backend?
Libgit2 supports different backends. See https://github.com/libgit2/libgit2-backends
This wiki uses dulwich which is a python git implementation, not libgit2 bindings like PyGit2. I can adapt the site to use either library I'm sure, but I don't believe either one support different backends besides filesystem and memory.
Solving this will enable this to become a 12-factor app, but I don't know how to do it.
The text was updated successfully, but these errors were encountered: