-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Move Gitrekt into own repo #83
Comments
Hi @kloenk, the Note that you will have to implement your own SSH, HTTP(S), etc. transport protocols around I don't have much time left currently to work on this right now (christmas coming and professional projects to finish). But I will come back to this issue later on and try to get things moving. Also, note that the |
Yep already created a test repo to play with it. But I think I will use gitaly, as ist rpc calls and has many helpful features. Just have to teach it that I'm not a gitlab server :) |
I would love to be able to use Gitrekt independently from GitLimo. That'd be a great contribution to the Elixir community as there no other good binding to Git for Elixir so far, AFAIK. |
@mekeor You can easily use Gitrekt independently already. Drop
in your mix deps :) |
@kloenk, what has been your experience with Gitaly? I'm building a localization platform with Git in its core, and I was debating between using Gitaly or building something on Elixir/Erlang. |
I sadly hat not much more time, working on it, so not sure of the current state. It looked usable, but some quirks to work around |
We are currently also looking at writing an git forge with elixir. We favor some different designs, like not using the erlang ssh module, indieweb integration and a plain json api.
If you could move gitrekt into its own repo, we could work on that part together.
The text was updated successfully, but these errors were encountered: