Tristans reply notwithstanding - a SSH GIT proxy would be useful in a variety of environments.
bryanhuntesl
tristan
Rebar3 Core Team
MarioFlach
You can use or extract different parts of the project to write a SSH Git proxy. The umbrella project has three separate apps:
The :gitrekt app provides:
- Git plumbing & porcelain commands (libgit2 wrapper using NIFs)
- Git wire-protocol implementation
- Git PACK format implementation
The :gitgud app provides the core functionalities and building blocks such as User, Repo and many other schemas. It also implement the SSHServer and SmartHTTPBackend both required to support Git over SSH/HTTP.
The :gitgud_web app provides the Phoenix application and a fully-featured GraphQL API.
I’m also very interested in a CI/CD solution for my project but need to finish/polish things first. There is GitHub - AlloyCI/alloy_ci: Continuous Integration, Deployment, and Delivery coordinator, written in Elixir. · GitHub which looks promising (based on GitLab CI runner).
1
MarioFlach
Thank you, I really enjoy working on this project! For me the interesting thing is that there is a lot of scaling possibilities.
I’m currently working with medium size repositories (elixir-lang > 15.000 commits, phoenix > 6.000 commits) and I’m quite happy with the performances so far. But it’s a completely different story to work on big repositories such as linux-kernel > 850.000 commits).
There are a few Git things that perform very slow. For example, getting the total number of ancestors from a given commit can take up to one second on large repositories. Even worse, getting the history for a specific blob or tree can take up to 20 seconds.
I’ve began to cache meta-informations each time a Git repository is pushed in order to optimise performances but there is still much to do…
3
wolfiton
@MarioFlach You are an ambitious person and with patience, I think you will do great things.
I am a beginner in elixir i only have one week in elixir but if I can help with your project in any way let me know.
As experience i only created some absinthe toy apps.
I want to learn more about elixir and phoenix and decided to make it my go to stack when it comes to web dev.
Currently learning vue and nuxt so if i can help with the frontend would be cool.
I also come with a node background and have some skills with graphql.
In any case good luck with the project.
2
MarioFlach
I’ve been working a lot on this project lately. Just released version 0.2.7.
Also I decided to publish the project on a dedicated server for testing purposes.
So here it is: https://git.limo
Or here if you want to browse some repositories:
This is pretty limited currently because you are not allowed to create new repositories. I need to provide monitoring tools and other things before letting anybody host their repositories.
Here’s a brief summary of the project’s current state:
Basic CRUD operations
- User registration/authentication
- with login/email - password credentials.
- with OAuth2.0 for GitHub and Gitlam.
- Email management:
- Each registered user need at least one verified email address in order to create new repositories and maintain other’s repositories.
- Each verified email address is used to associate Git commits. This is also the case for GPG signed commits.
- The primary email address is also used to retrieve a user’s Gravatar.
- SSH and GPG key management:
- We support Git over SSH and HTTPS. By adding SSH public keys, a user can authenticate without the need of a password.
- GPG public keys are used to verify that a Git commit has been signed by a given user. In order to show the verification icon:
- The committer’s email must match a verified email address
- The committer’s email must also match the GPG key email address
- Repository management:
- Users can create repositories if they have at least one verified email address.
- Each repository can have multiple maintainers with read/write/admin rights.
Git Repositories
We support both HTTPS and SSH transport protocols. While HTTPS support Basic Authentication via credentials. SSH supports authentication via public key and password.
Access to repositories depend on the user’s authorisations:
- Anybody can view/clone a public repo.
- Only owner and maintainers can view/clone a private repo.
- Only owner and maintainers with at least
:writeaccess can write/push to a repo. - Only owner and maintainers with
:adminaccess can edit settings of a repo.
Browsing repositories is similar to GitHub/GitLab. You can browse trees, view blobs (with syntax-highlighting), walk the commit history, walk the commit history for a given tree/blob, display diffs, etc.
Accessing a Git repository content is done via the GitRekt.GitAgent abstraction. Basically the agent provides an API to manipulate Git objects and refs.
The nice part here is that the access to a repository can be done from multiple processes simultaneously (by wrapping the NIFs resources in a GenServer and serialising function calls).
This will be important when implementing support for clustering aka. distributing repositories on multiple nodes.
The GitRekt.GitAgent provides two different modes:
:inproc- callingGitRekt.Gitfunctions (NIFs) directly.:shared- serialise function calls throughGenServer.
The GitRekt.GitRepo protocol helps to implement custom logic (clustering) for both modes. Currently, only GitGud.Repo implements this protocol.
GraphQL API
The available GraphQL API is quite fully featured. It also provide subscriptions via Phoenix Websockets.
Issues and reviews
There is no issue system at the moment. I hope to get started with issues soon.
I also want to provide a review mechanism, basically the possibility to review changes across commits. Currently, any registered user can comment on any commit. Comments are stored globally (shown at the end of a diff) or on a per-line basis.
Wiki
I’ve played a little bit with a Git based Wiki implementation. But this will come in a later future.
14
LTheGreats
The project looks really cool. The front page even has my favorite language, lorem ipsum! Seriously though, this is an awesome use for elixir and looking through this project’s source code is interesting and fun.
2
MarioFlach
Wow I didn’t know about Xgit. Looks very promising 
I really like the repository storage abstraction. Is Xgit.Repository.OnDisk fully compatible with the Git filesystem storage format?
My approach is very different one, I wrote NIFs to wrap a good part of libgit2. I also wrote an experimental storage backend to work with libpq.
Ditching libgit2 all together for an Elixir based Git implementation would be 
4