Is it your roadmap - to extract git server functionality in separate hex packages?
I’m trying to make a small project which will use git server approaches (it means that you can push something to it), but cloning the whole GitGud with significant changes in web part seems to be very bad idea, because it’s impossible to pull new updates with git-server part in the future.
I can help with contributing to git-server part with documentations, testing and use experience, if it will be separated.
Any chance of putting up a demo site somewhere so we can see it without installing it locally?
It’s an umbrella application with three apps:
:gitrekt – Git NIFs, wire-protocol and packfile implementation.:gitgud – Ecto schemas and queries for users and repositories, authorization and Git HTTP and SSH transport protocol implementation.:gitgud_web – Web application and GraphQL.The dependency graph looks as follow:
gitrekt <- gitgud <- gitgud_web
Currently, I do not plan to split the project into multiple independent apps. At least not until I release a more stable version.
If you wish to do so, you can extract :gitrekt and :gitgud and use them independently without Phoenix and Absinthe dependencies.
I’m doing my best to release a more polished version soon. In the long-term, a public launch is planned and moving the project’s codebase to it own service will be the first logic step. Stay tuned =)
@MarioFlach impressive !
I’ve got a question. When building Erlang/Elixir software in docker - private repositories (git ssh) are always a problem. The current options are:
I’ve had an idea of a possible solution. A ssh git proxy running in the same docker network, with the hostname github.com
I was wondering could some part of your project be reused to achieve this goal - it would really improve the CI story for Erlang/Elixir vs go (where all the dependencies are just ‘vendored’ (copy-n-pasted) into the repository.
+-------------------------Network 'ci'-----------------------------+
| |
| |
| +----------------+ Fetch dependency +------------------+ |
| | | (git ssh) | Docker container | |
| | docker build +----------------------> (github.com) | |
| | | | | |
| +----------------+ +------------------+ |
| | |
| | |
+------------------------------------------------------------------+
|
|
+--------------------------+ |
| | |
| Github.com +<---+
| | Fetch and cache
| |
| |
+--------------------------+
I’m thinking of tools like :
Thanks,
Bryan
Checkout docker 19.03 (not GA as of this comment but there are release candidates) for secure ways of doing the id_rsa “copy”. Note you can also use .netrc file to use https instead of ssh for cloning from github.
There is a good blog post about using it for ssh and secrets for netrc here https://medium.com/@tonistiigi/build-secrets-and-ssh-forwarding-in-docker-18-09-ae8161d066
You could also use it for hexpm:
RUN --mount=type=secret,id=hex.config,target=/root/.config/rebar3/hex.config rebar3 compile
Then run with with:
$ docker build --secret id=hex.config,src=~/.config/rebar3/hex.config .
There is also a new build cache that allows you to store artifacts like fetched hex deps separate from the image and automatically bring them in at build time. Plus mounting . instead of COPY . ..
I got it working but was hacky to do having rebar3’s _build be stored outside of ./ so it could be cached by the new docker build cache and then you don’t lose your built dependencies or git clones either. I’m sure similar can be done with mix.
I have written all this up with more details and examples but I’m still waiting for 19.03 to be released before publishing 
Very interesting an cool project @MarioFlach , it makes you think that sky is the limit with elixir and phoenix.
Thanks Tristan - I see in Docker for Mac edge release notes - Docker Desktop release notes | Docker Docs
Upgrades
* [Docker 19.03.0-rc2](https://github.com/docker/docker-ce/releases/tag/v19.03.0-rc2)
Oh joy - have you managed to get the secrets stuff working on OSX? I reached out a couple of months ago and there was no progress.
B