{"id":5532,"date":"2013-09-19T14:44:54","date_gmt":"2013-09-19T11:44:54","guid":{"rendered":"http:\/\/railsware.com\/blog\/?p=5532"},"modified":"2021-08-11T18:10:08","modified_gmt":"2021-08-11T15:10:08","slug":"taming-the-git-daemon-to-quickly-share-git-repository","status":"publish","type":"post","link":"https:\/\/railsware.com\/blog\/taming-the-git-daemon-to-quickly-share-git-repository\/","title":{"rendered":"Taming The Git-Daemon To Quickly Share Git Repository"},"content":{"rendered":"I was once in a hurry to share GitHub repository with a colleague who didn’t have access to it and we decided to use local git-daemon. However, handling all the little quirks that would make it work took a lot more efforts than just dropping a repository archive via Skype.\n\nFrom this article you will learn how to easily share read\/write access to the local git repository. Additionally, I will share two simple aliases for git that will make this task a real no-brainer for anyone.\n

Disclaimer<\/h2>\nPlease note that this is an insecure way of sharing access to git repository and should be used only in a friendly LAN-environment. If you need secured solution, consider using SSH-protected way<\/a>.\n

Sharing read-only access<\/h2>\nNext command shares read access(clone\/pull) to any repository in current directory:\n
$ git daemon --base-path=. --export-all --reuseaddr --informative-errors --verbose\n<\/pre>\nWhere:\n
    \n \t
  • –export-all – shares all the repositories in a folder from “–base-path” option<\/li>\n \t
  • –base-path=. – daemon looks for repositories in a current directory(“.”)<\/li>\n \t
  • –reuseaddr – allows to restart server quickly<\/li>\n \t
  • –informative-errors – provides cleaner error message for clients<\/li>\n \t
  • –verbose – notifies about each operation with the repository<\/li>\n<\/ul>\n
    Sample flow<\/h3>\n1) Run git-daemon in directory with your repos:\n
    $ cd my-repos\n$ ls\nfacebook-killer better-twitter instapound\n\n$ git daemon --base-path=. --export-all --reuseaddr --informative-errors --verbose\n[8322] Ready to rumble\n<\/pre>\n2) Now clients can clone\/pull this repository:\n
    $ git clone git:\/\/127.0.0.1\/facebook-killer\nCloning into 'facebook-killer'...\nremote: Counting objects: ...\n...\n\n$ git pull\nAlready up-to-date.\n<\/pre>\nInstead of the “127.0.0.1” client should use the IP of your computer.\n
    Sharing push access<\/h2>\nAdd “–enable=receive-pack” option and git-daemon starts supporting push access:\n
    $ git daemon --base-path=. --export-all --enable=receive-pack --reuseaddr --informative-errors --verbose\n<\/pre>\nThere is one quirk: client can’t push into your active git branch. Before pushing, user on the server should change the branch, if client wants to push to this branch.\n\nAnother option can be for the client to create a new branch and push it to your server. Then you can merge it into a required branch.\n
    Sample flow<\/h3>\n1) Run git-daemon in read\/write mode:\n
    $ git daemon --base-path=. --export-all --enable=receive-pack --reuseaddr --informative-errors --verbose\n[8322] Ready to rumble\n<\/pre>\n2) Client clones repository:\n
    $ git clone git:\/\/127.0.0.1\/facebook-killer\nCloning into 'facebook-killer'...\nremote: Counting objects: ...\n...\n<\/pre>\n3) Client branches-off, makes changes and pushes back new branch:\n
    $ git checkout -b sharing\n# made some changes ...\n$ git commit -am \"add sharing feature\"\n$ git push -u origin sharing\n...\n* [new branch]      sharing -> sharing\n...\n<\/pre>\n4) Now on Server you can merge this branch:\n
    $ git checkout master\n$ git merge sharing\n<\/pre>\n
    Sharing only one repository<\/h2>\nIf you want to share only some repositories, you’ll need to remove “–export-all” option and create “git-daemon-export-ok” file in .git directory of the appropriate repositories.\n
    Sample flow<\/h3>\n1) Create magic file:\n
    $ cd my-repos\n$ ls\nfacebook-killer better-twitter instapound\n\n$ touch facebook-killer\/.git\/git-daemon-export-ok\n<\/pre>\n2) Run git-daemon without “–export-all” option:\n
    $ git daemon --base-path=. --enable=receive-pack --reuseaddr --informative-errors --verbose\n<\/pre>\n3) Client can’t access non-shared repository:\n
    $ git clone git:\/\/127.0.0.1\/better-than-twitter\nCloning into 'better-than-twitter'...\nfatal: remote error: repository not exported: \/better-than-twitter\n<\/pre>\n4) Client can access shared repository:\n
    $ git clone git:\/\/127.0.0.1\/facebook-killer\nCloning into 'facebook-killer'...\nremote: Counting objects: ..., done.\n...\n<\/pre>\n
    Making life simpler with aliases<\/h2>\nLet’s create git aliases for read-only and read\/write sharing. Here is what it should look like in .gitconfig:\n
    # .gitconfig\n[alias]\n    serve = !git daemon --base-path=. --export-all --reuseaddr --informative-errors --verbose\n    hub = !git daemon --base-path=. --export-all --enable=receive-pack --reuseaddr --informative-errors --verbose\n# ...\n<\/pre>\nNotice “!”-symbol in front of the aliases. This is a way to alias external shell command, and with this trick we can call these commands outside of git repository.\n\nNext commands automatically put these aliases into .gitconfig:\n
    $ git config --global alias.serve '!git daemon --base-path=. --export-all --reuseaddr --informative-errors --verbose'\n$ git config --global alias.hub '!git daemon --base-path=. --export-all --enable=receive-pack --reuseaddr --informative-errors --verbose'\n<\/pre>\nNow with “git serve” you can share read access and with “git hub” – read\/write access to our repositories. “git serve” resembles Mercurial “hg serve” which performs exactly the same operation. And “git hub” feels to be just right for read\/write sharing, don’t know why.\n\nOnce the aliases are added, we can run and see “hub” command in action:\n
    $ git hub\n[19178] Ready to rumble\n<\/pre>\nYay, it works!\n\nThat’s it, and as I promised – it’s a real no-brainer to share anything using these magic aliases.","protected":false},"excerpt":{"rendered":"
    I was once in a hurry to share GitHub repository with a colleague who didn’t have access to it and we decided to use local git-daemon. However, handling all the little quirks that would make it work took a lot more efforts than just dropping a repository archive via Skype. From this article you will…<\/p>\n","protected":false},"author":25,"featured_media":9467,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"coauthors":["Sergii Boiko"],"class_list":["post-5532","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"aioseo_notices":[],"categories_data":[{"name":"Engineering","link":"https:\/\/railsware.com\/blog?category=development"}],"post_thumbnails":"https:\/\/railsware.com\/blog\/wp-content\/themes\/railsware\/vendors\/images\/article-thumbnail-default.jpg","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/5532","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/comments?post=5532"}],"version-history":[{"count":58,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/5532\/revisions"}],"predecessor-version":[{"id":13931,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/5532\/revisions\/13931"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media\/9467"}],"wp:attachment":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media?parent=5532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/categories?post=5532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/tags?post=5532"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/coauthors?post=5532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}