ServerAdmin /var/log/apache2/git_apache_error.log $> cd /etc/apache2/sites-availableĩ) Add (or alter) the existing configuration of file, which you just created, based on the next configuration. A fast way to configure your Apache site(and test immediately) is to copy the existing configuration of Apache and make the required configuration changes. Assume you already have a domain name ( e.g. $> a2enmod Ĩ) Now you only need to configure Apache site and you are ready. This can be easily done on Debian with a2enmod command, where it create symbolic links in the next directory. $> openssl req -x509 -nodes -days 999 -newkey rsa:2048 -keyout mygit_ssl.key -out mygit_ssl.crtħ) Also, we need a few modules to be enabled on Apache, so make sure mod_ssl, mod_cgi, mod_alias, and mod_env are enabled.
Fill all the fields you like that the next command requires. On the same directory create the certificate and the private keys pair. So, I created a self signed SSL certificate using openssl. $> mkdir /etc/gitdataĦ) I choose to use secure HTTP for Git communication. Create a specific directory and file, with restricted privileges to www-data user, in order to keep git users and passwords. So, using this strategy we can define as many Git users as we need, without creating Unix users. On Debian, when you install apache2 package, user $> chown -R These users are irrelevant to Unix users of OS. $> cd /opt/allgit/reposĤ) We will use Apache 2 HTTP server to support HTTP(S) for Git. $> apt-get install git apache2 apache2-utils opensslĢ) As we need many Git repositories, we create a base directory that all repositories will be included.ģ) Create a bare Git repository, where developers can pull and push code. Using these clever cgi scripts, which now are part of stable Git, we can easily setup a Git server that supports read/write via HTTP(S).ġ) Install all required packages on Debian: $> su. Almost 2 years ago Smart HTTP Transport came up. Until recently, Git HTTP(S) was working only for read actions (only clone, fetch, pull, …). Many people are behind a firewall, which most of times permit access only to HTTP(S). Git supports 4 network protocols to transfer data: SSH, Local, Git, and HTTP(S). I will describe here a fast and minimal configuration of how to turn a Debian GNU/Linux box to a Git server that supports read and write actions via HTTP(S). I guess you already know the advantages of Git over Subversion, as there are too many discussions for this subject. Three months ago we decided to move our projects to Git.
0 kommentar(er)
