Bug #6663
Updated by Brett Smith almost 9 years ago
The install docs don't say much about setting up git repositories. They should explain: at: http://doc.arvados.org/install/install-arv-git-httpd.html * Git repositories must live on the same host as the API server. The user account running the API server must have read access Require there to all those repositories. * In production, we use gitolite to create repositories and manage their permissions via SSH. We use the script at source:docker/api/update-gitolite.rb to do that. Link to the gitolite installation documentation for details. * If you don't want to use Gitolite, you don't have to do that. You don't even have to serve repositories via SSH at all. But you'll at least need to write be a script that polls Arvados SSH repositories and manages real repositories on disk accordingly. We also recommend that you create a @git@ git user that owns all repositories, just to simplify permissions. * Whatever script you choose, set up a cron job to run it regularly. We run it every 2 minutes. Include an example entry that shows @update-gitolite.rb@ being run every two minutes. You can choose any interval, `sudo -u git` but did not mention creating the more often you run it, the better repositories on disk will match Arvados' records. All this should be added in a new section of the API server installation documentation. Once that's done, go through the install-git-server page and make sure instructions there are consistent with these steps, making any updates necessary. At the very least, after the @run@ script that uses @sudo -u git@, note that this follows our recommendation to set up a dedicated @git@ git user (and it does not seem to own the repositories. The service should run as whatever user owns the repositories occur automatically when packages are installed, at least on disk. Ubuntu 12.04).