https://www.openembedded.org/api.php?action=feedcontributions&user=130.133.50.244&feedformat=atomOpenembedded.org - User contributions [en]2024-03-28T23:59:04ZUser contributionsMediaWiki 1.29.0https://www.openembedded.org/index.php?title=GitServerSetup&diff=718GitServerSetup2008-10-16T11:43:27Z<p>130.133.50.244: /* Service Infrastructure */</p>
<hr />
<div>= Git Service Overview =<br />
<br />
Our git services are hosted on git.openembedded.net. There is a user called git and the repositories are located within /home/git/repositories. There is one repository for managing gitosis itself and currently one called openembedded.git with our metadata. git, webgit and gitosis are installed as debian packages, /etc/gitweb.con is pointing to /home/git/repositories. git-daemon is running as a serv the service configuration can be found in /var/services/git-daemon/run and it points to /home/git/repositories as configuration as well.<br />
<br />
<br />
= Service Infrastructure =<br />
== gitosis ==<br />
Installed with debian. Clone :gitosis-admin if you are part of the admin team<br />
<br />
== gitweb ==<br />
/etc/gitweb.conf, it will list repositories from /home/git/repositories that have the gitweb flag in the object dir. This is the case for openembedded.git<br />
<br />
== git-daemon ==<br />
It is running as runsv service. This means there is a /var/run/service/git-daemon/ directory and inside the run file is the command of git-daemon. As basepath it is pointing to /home/git/repositores. Everything with a special flag inside the repository will be exported via git-daemon. This is the case for the openembedded.git repository<br />
<br />
<br />
= Managing and Troubleshooting =<br />
== Adding new keys ==<br />
You will need admin rights. Then you can git-clone git@git.openembedded.net:gitosis-admin. You can add a key to keydir. Use name.pub for the key, then you can add name to the gitosis.conf. Commit your change and then git-push and the guy is able to push afterwards.<br />
<br />
== How the commit mails and ciabot work ==<br />
In the openembedded.git repository there is the activated "update" hook. At the end of this script git-notify in /home/git is called. git-notify was copied from the wine project at a certain date, see the top of the file.<br />
<br />
== Troubleshooting ==<br />
Add loglevel = DEBUG below [gitosis] (2nd line). Then you get more output when login fails or no permissions are given.</div>130.133.50.244https://www.openembedded.org/index.php?title=GitServerSetup&diff=717GitServerSetup2008-10-16T11:43:03Z<p>130.133.50.244: New page: = Git Service Overview = Our git services are hosted on git.openembedded.net. There is a user called git and the repositories are located within /home/git/repositories. There is one repos...</p>
<hr />
<div>= Git Service Overview =<br />
<br />
Our git services are hosted on git.openembedded.net. There is a user called git and the repositories are located within /home/git/repositories. There is one repository for managing gitosis itself and currently one called openembedded.git with our metadata. git, webgit and gitosis are installed as debian packages, /etc/gitweb.con is pointing to /home/git/repositories. git-daemon is running as a serv the service configuration can be found in /var/services/git-daemon/run and it points to /home/git/repositories as configuration as well.<br />
<br />
<br />
= Service Infrastructure =<br />
== gitosis ==<br />
Installed with debian. Clone :gitosis-admin if you are part of the admin team<br />
<br />
== gitweb ==<br />
/etc/gitweb.conf, it will list repositories from /home/git/repositories that have the gitweb flag in the object dir. This is the case for openembedded.git<br />
<br />
== git-daemon ==<br />
It is running as runsv service. This means there is a /var/run/service/git-daemon/ directory and inside the run file is the command of git-daemon. As basepath it is pointing to /home/git/repositores. Everything with a special flag inside the repository will be exported via git-daemon. This is the case for the openembedded.git repository<br />
<br />
<br />
<br />
== Adding new keys ==<br />
You will need admin rights. Then you can git-clone git@git.openembedded.net:gitosis-admin. You can add a key to keydir. Use name.pub for the key, then you can add name to the gitosis.conf. Commit your change and then git-push and the guy is able to push afterwards.<br />
<br />
== How the commit mails and ciabot work ==<br />
In the openembedded.git repository there is the activated "update" hook. At the end of this script git-notify in /home/git is called. git-notify was copied from the wine project at a certain date, see the top of the file.<br />
<br />
== Troubleshooting ==<br />
Add loglevel = DEBUG below [gitosis] (2nd line). Then you get more output when login fails or no permissions are given.</div>130.133.50.244