{"thread":{"id":"21443","subject":"Gitolite update","startedAt":"2009-10-31T06:02:38Z","lastAt":"2009-10-31T06:02:38Z","messageCount":1,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"126513","messageId":"2e24e5b90910302302n6e4e68ct43ea1bacc18d1266@mail.gmail.com","threadId":"21443","inReplyTo":null,"subject":"Gitolite update","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-10-31T06:02:38Z","receivedAt":"2009-10-31T06:02:38Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"This is an update on gitolite, an ssh-based access control tool for\nusing git in a typical corporate environment.  The latest version is\nalways at git://github.com/sitaramc/gitolite.git\n\nWhile still remaining upward compatible with the \"inspiration\" project\n(gitosis), the extra features now form the largest section in\nhttp://github.com/sitaramc/gitolite/blob/pu/doc/3-faq-tips-etc.mkd.\nThis was mostly the result of users asking for features they wanted, so\nplease take a look to see if something there strikes your fancy.\n\n    [However, the 2 programs that do the actual access control *still*\n    total only about 90 lines; I firmly intend to keep those less than\n    100 to make them easy to audit for security.]\n\nSignificant additions since the last update\n-------------------------------------------\n\nInstalls/upgrades\n\n  * The easy install script is also good for upgrades.  The new \"-q\"\n    option is particularly useful, and makes an upgrade really quick and\n    \"one command\".\n\n    Remote admin mode (where you make config changes in a clone of the\n    gitolite-admin repo, and push them to the server) is now the\n    *default*.  I think I managed to put enough ssh intelligence into\n    the ssh aspect to make this finally work without pain, and people on\n    #git have said it does work (i.e., it's not just me claiming it ;-)\n\nConfig file maintenance\n\n  * Large config files (when you have many, many, repos) can be split up\n    and delegated to different people.  The main config file can give a\n    specific user the authority to manage a specific group of repos, and\n    that user can then maintain the access control for those repos\n    independently.\n\n  * Config files are also checked for mismatches in pubkeys and\n    usernames, which is good for catching typos early.\n\nDocumentation etc\n\n  * The documentation, help text, and messages that come out have had\n    numerous changes based on user feedback on #git.  Like in the easy\n    install script, a lot of effort has gone into the ssh aspect.\n\nOther (minor) updates\n---------------------\n\n  * Supports git installed outside the normal $PATH (on the server).\n    Without this, *all* your users would have to specify the upload-pack\n    and receive-pack program paths, either by setting config variables\n    or using \"-u\", \"--exec\" etc. in the clone/push commands.\n\n  * Trying a plain ssh to your gitolite account now tells you what repos\n    you have access to, instead of a (largely useless) error message\n    about needing SSH_ORIGINAL_COMMAND.  This sounds like a gimmick...\n    until you actually need it :)\n\n  * I've finally started tagging releases, and now an install or an\n    upgrade done from a clone will record the version number.  When you\n    upgrade, it tells you you're upgrading from version foo to version\n    bar.\n\n  * When specifying repos in subdirectories (foo/bar/baz.git) you no\n    longer have to manually create foo/bar on the server first.\n\nRecap of older features (for completeness)\n------------------------------------------\n\n  * per-branch permissions, including fine-grained control over \"rewind\"\n  * install without root access on any Unix\n  * simpler but much more powerful config file syntax\n  * more comprehensive logging\n  * \"personal\" namespace prefix for each user\n  * \"deny\" rights in the config file (in the \"rebel\" branch)\n\nQuestions and support\n---------------------\n\nI'm often on #git, subject to my living in UTC+0530 time, and email is\nalso welcome (sitaramc@gmail.com is preferred, but\nsitaram.chamarty@tcs.com may get my attention quicker).  If you log an\nissue on github, please also send an email; I am checking github more\noften now (having missed two issues for many days) but it's not as\nfrequent as I would have liked.\n\n-- \nSitaram\nsitaramc@gmail.com / sitaram.chamarty@tcs.com\n"}]}