{"thread":{"id":"28649","subject":"\"trying out\" gitolite with minimum impact on a system","startedAt":"2011-10-11T17:19:06Z","lastAt":"2011-10-12T07:52:47Z","messageCount":3,"participants":["Sitaram Chamarty","Philippe Vaucher"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"177379","messageId":"CAMK1S_g5CnP+vrE71cqMgcjpj8ocE+wdtA2vPjeaXGCRNt25Dw@mail.gmail.com","threadId":"28649","inReplyTo":null,"subject":"\"trying out\" gitolite with minimum impact on a system","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-10-11T17:19:06Z","receivedAt":"2011-10-11T17:19:06Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"(This is kind of a record for me, 2 gitolite related emails to the git\nML in less than a month)\n\nIf you were in the position of vaguely thinking gitolite may be useful\nto you but lacked the time to actually install it to try things out,\nthis may help.\n\n----\n\nSome folks want to be able to try gitolite's access control features,\nplay with the configuration language, and so on, but to actually\n*install* it seems like a \"commitment\" of some kind.\n\nGitolite has always had the ability to be installed *entirely* within\none Unix userid.  Plus, the homegrown test suite I've been using for a\nwhile now has always simulated different \"gitolite users\" with a bit\nof ~/.ssh/config magic.\n\nSo I just combined the two, and made the client also be on the same\nUnix userid, resulting in this:\nhttp://sitaramc.github.com/gitolite/t/README.html#_playing_with_gitolite\n\nBriefly, it boils down to this: create a user, log in as that user,\nclone gitolite, run *one* command.  Done.\n\nAfter that, entirely within that user, you have an admin user and six\nnormal users, to do with as you please.  You emulate different users\nsimply by using a different username in the URL, like \"git clone\nu1:reponame\" versus \"git clone u2:reponame\".\n\nThis gives you a chance to play with the myriad access control\nfeatures gitolite has.\n\nWhen done, delete that user and your system is back where it was.\n\n-- \nSitaram\n"},{"id":"177427","messageId":"CAGK7Mr6cnP6QQwGswWwQYiGR2_BUjMPz+VsygQXb0Voehm+akg@mail.gmail.com","threadId":"28649","inReplyTo":"CAMK1S_g5CnP+vrE71cqMgcjpj8ocE+wdtA2vPjeaXGCRNt25Dw@mail.gmail.com","subject":"Re: \"trying out\" gitolite with minimum impact on a system","fromName":"Philippe Vaucher","fromEmail":"philippe.vaucher@gmail.com","sentAt":"2011-10-12T06:15:42Z","receivedAt":"2011-10-12T06:15:42Z","isPatch":false,"sender":{"key":"philippe.vaucher@gmail.com","avatar":null},"body":"> After that, entirely within that user, you have an admin user and six\n> normal users, to do with as you please.  You emulate different users\n> simply by using a different username in the URL, like \"git clone\n> u1:reponame\" versus \"git clone u2:reponame\".\n\nHum, except if I missed something the classic way to use gitolite is\nto always clone using the same user (git@host:repository.git), and the\n\"real\" identification is done by the ssh keys (which means that\ncontrary to plain ssh you lose the ability to have two users with the\nsame ssh key, which should never happen anyway).\n\nBut maybe you're refering to an alternate authentification mechanism\nwithin gitolite I'm unaware of.\n\nPhilippe\n"},{"id":"177429","messageId":"CAMK1S_juQRRNhCMDx4Wdp+QwAZBQBvBYYQ06AdS_P2fdtLqBtg@mail.gmail.com","threadId":"28649","inReplyTo":"CAGK7Mr6cnP6QQwGswWwQYiGR2_BUjMPz+VsygQXb0Voehm+akg@mail.gmail.com","subject":"Re: \"trying out\" gitolite with minimum impact on a system","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-10-12T07:52:47Z","receivedAt":"2011-10-12T07:52:47Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Wed, Oct 12, 2011 at 11:45 AM, Philippe Vaucher\n<philippe.vaucher@gmail.com> wrote:\n>> After that, entirely within that user, you have an admin user and six\n>> normal users, to do with as you please.  You emulate different users\n>> simply by using a different username in the URL, like \"git clone\n>> u1:reponame\" versus \"git clone u2:reponame\".\n>\n> Hum, except if I missed something the classic way to use gitolite is\n> to always clone using the same user (git@host:repository.git), and the\n> \"real\" identification is done by the ssh keys (which means that\n> contrary to plain ssh you lose the ability to have two users with the\n> same ssh key, which should never happen anyway).\n>\n> But maybe you're refering to an alternate authentification mechanism\n> within gitolite I'm unaware of.\n\nyou should read \"entirely within that user\" as \"entirely within that\nnew, possibly throw-away, Unix userid you created\".  This is meant to\nfit with the subject line's \"minimum impact on a system\" phrase.\n\nregards\n\nsitaram\n"}]}