#Simple git server software
#Simple git server code
#Simple git server password

#Simple git server software

For unreleased software (between tags), the version identifier should provide enough information to help developers recreate the same tree, while also giving them an idea of roughly how old the tree is (after version 1.2, before version 1.3). 'myproject-1.2' instead of just '1.2'), in which case the tool needs to strip the tag prefix to extract the version identifier. Some projects use tag names that include more than just the version string (e.g. For released software, the version identifier is closely related to a VCS tag. Making a new release should be as easy as recording a new tag in your version-control system, and maybe making new tarballs. The goal is to remove the tedious and error-prone 'update the embedded version string' step from your release process. This is a tool for managing a recorded version number in distutils-based python projects. Gogs - Self Hosted Git Service, written in Go.Python-versioneer - version-string management for VCS-controlled trees.

#Simple git server code

GitLab - Project management and code hosting application, written in Ruby.

Gitea - Painless self-hosted Git service.

cgit - A web interface for git written in plain C.

Gitweb - the default web interface that comes with Git.

Note that if you are willing to create user accounts for all of the people that should have access to the repositories and do not need access control at the level of git objects (like branches), you can also use standard file permissions for access control.

Gitosis - Software for hosting Git repositories, written in Python.

Gitolite - An access control layer on top of Git, written in Perl.

The service uses the -export-all and -base-path parameters to serve all repositories placed in /srv/git/.įor fine-grained access control, the following solutions are available: The Git daemon ( git-daemon(1)) can be started with git-daemon.socket. The Git protocol is not encrypted or authenticated, and only allows read access. Note: Make sure that Apache can read and write to your repositories.įor more detailed documentation, visit the following links: You might want to specify the clone URL as This works for the initial clone but for a subsequent push you get an error message in your error log stating that the destination URL is handled by a different repository.

#Simple git server password

Password topsecret $ > git push origin mainįrom 03f8860418facfbecedd5e0a81b480131b31bcba The only solution that works so far is editing the ~/.netrc (obviously git uses curl for http): Running a git credential cache does not help. Appearently the git client has a problem passing the username and password for all subsequent requests. Oh noes! For some reason PROPFIND reports 401 Unauthorized and that's all. Make some changes, add, commit, and push:Įrror: Cannot access URL, return code 22 Everyone who has an password entry in the htaccess file can push. You might have noticed that I added HTTP Basic Authentication to have at lease some means of access control.

chown the repo to be owned by http:http.

run git update-server-info in the bare repo.

git clone -bare /path/to/myrepo myrepo.git.

Now do the ususal steps when preparing a git repo for the server:

etc/nginx/nf dav_ext_lock_zone zone=general:10m

Add the specified locking zone to the http section of your config: Here is an example location block:Īuth_basic_user_file /etc/nginx/htpasswd ĭav_ext_methods PROPFIND OPTIONS LOCK UNLOCK Pushing via WebDAV also requires Locking. 'Dumb' in this context means that only WebDAV is involved in pulls and pushes.įollow the basic WebDAV instructions for nginx. Change the base path when home directory is corrected: In order for git to serve the repositories, the -base-path in need to be changed to /srv/git if the repositories are served from git's home directory.Change the home directory: In order for ssh to be able to read /srv/git/.ssh/authorized_keys, the home directory for git in /etc/passwd needs to be changed from / to /srv/git.When securing the git server created using the instructions in #General with the instructions of this clause ( #SSH), the following additional steps are needed on Arch: This is done by replacing the default login shell by git-shell.

You are able to secure the SSH user account even more allowing only push and pull commands on this user account. Use chage to remove the expiration condition, e.g. Step by Step Guide on Setting Up git Server describes setting up an unsecured server on Arch.īy default, the git user is expired ('Your account has expired please contact your system administrator'). Refer to Git on the Server - The Protocols for a detailed description along with pros and cons.