Skip to content
Commits on Nov 25, 2009
  1. auth: print permissions for @all also

    I don't have a use for "@all" at all (pun not intended!) other than the
    "testing" repo, but <teemu dot matilainen at iki dot fi> sent in a patch
    to mark those repos with "R" and "W" in the permissions list, and I
    started thinking about it.
    
    This could actually be useful if we *differentiated* such access from
    normal (explicit username) access.  From the "corporate environment"
    angle, it would be nice if a project manager could quickly check if any
    of his projects have erroneously been made accessible by @all.
    
    So what we do now is print "@" in the corresponding column if "@all" has
    the corresponding access.
    
    Also, when someone has access both as himself *and* via @all, we print
    the "@"; printing the "R" or "W" would hide the "@", and wouldn't
    correctly satisfy the use case described above.
    Sitaram Chamarty committed Nov 25, 2009
  2. doc/3: $repo_base -> $projectroot; honor @all in perm check

      - it appears that what we call $repo_base, gitweb already needs as
        $projectroot
      - allow read of repos defined as readable by @all
    
    plus some minor declaration changes to make the sample code work as is
    
    (thanks to teemu dot matilainen at iki dot fi)
    Sitaram Chamarty committed Nov 25, 2009
Commits on Nov 24, 2009
  1. easy install: when the first install doesn't go right...

    We detect an upgrade situation by the presence of
    $GL_ADMINDIR/conf/gitolite.conf -- if it exists, we reason, this is not
    a fresh install.  And if so we skip setting up PTA, and the initial
    clone.
    
    Well, turns out this is not always true.  I've had a few cases where the
    first install didn't go right, but left enough stuff in to make the
    subsequent attempt think this is an upgrade.
    
    [This mostly happened to me when I was testing the "oldgits" branch, and
    also when I was making it work from msysgit I think... regardless of
    why, it'd be good to fix]
    
    So this changes the flow somewhat.  Now the *only* difference between a
    fresh install and an ugrade is the "initial_conf_key" function call (you
    don't want to overwrite an existing conf file or keydir!)
    Sitaram Chamarty committed with Sitaram Chamarty Nov 22, 2009
  2. minor doc/message updates/clarifications

    Sitaram Chamarty committed with Sitaram Chamarty Nov 22, 2009
Commits on Nov 23, 2009
  1. compile: (oopsies...) plug security hole in delegation feature

    I was trying to determine how close gitolite can come to the ACL model
    of a proprietary product called codebeamer, and one of the items was how
    to make a "role" (like QA_Lead) have different "members" in different
    projects.
    
    I then realised delegation already does that!  Which is great, but as I
    thought about it more, I realised...  well, we'll let the in-code
    comments speak for themselves :-)
    
    Anyway, all it needed was a 1-line fix, luckily... <phew>  And it would
    have only affected people who use delegation.
    Sitaram Chamarty committed Nov 23, 2009
  2. compile: make compiled config be key-sorted

    makes debugging access changes much easier
    
    (doh!  why didn't I do this earlier!)
    Sitaram Chamarty committed Nov 23, 2009
Commits on Nov 19, 2009
  1. serverside install/ga-hook: solaris compat

    Sitaram Chamarty committed Nov 19, 2009
  2. easy install (+doc): make it run from msys. Here's how:

      - all $HOME/blah becomes "$HOME/blah" (bl**dy "Documents and Settings" crap)
      - replace bash regex with perl, and in one case replace the check with
        something else
      - rsync changed to appropriate scp
      - since we no longer insist on running from a specific directory, create
        tmpgli dir *after* you cd to the right place
    Sitaram Chamarty committed Nov 18, 2009
Commits on Nov 18, 2009
  1. all src/ and conf/: force crlf=input via gitattributes

    msysgit needs this on the initial clone, so it has to be on master.  It
    doesn't seem to "apply" the gitattributes if you checkout a different branch
    later that has that setting; didn't investigate why
    Sitaram Chamarty committed Nov 18, 2009
  2. install doc: server and client requirements spelled out

    Sitaram Chamarty committed Nov 18, 2009
  3. README, doc/3: gitweb "description" feature

    Sitaram Chamarty committed Nov 18, 2009
Commits on Nov 17, 2009
  1. update hook: 'sub check_ref' to prepare for rebel+

    factor out the code to check $ref into a sub; will help rebel+, which
    wants (horrors!) to restrict based on PATH names too!
    Sitaram Chamarty committed Nov 16, 2009
Commits on Nov 13, 2009
  1. all src: (please read full commit message): allow local admin-defined…

    … hooks
    
    You can now add your own hooks into src/hooks/ and they get propagated
    along with the update hook that is present there now.  Please read the
    new section in the admin document, and make sure you understand the
    security implications of accidentally fiddling with the "update" script.
    
    This also prompted a major rename spree of all the files to be
    consistent, etc.  Plus people said that the .sh and .pl suffixes should
    be avoided (and I was feeling the same way).  I've also been
    inconsistent with that "gl-" prefix, so I cleaned that up, and the 00-
    and 99- were also funny animals.
    
    Time to get all this cleaned up before we get 1.0 :)
    
    So these are the changes, in case you're looking at just the commit
    message and not the diffstat:
    
        src/pta-hook.sh -> src/ga-post-update-hook
        src/conf-convert.pl -> src/gl-conf-convert
        src/00-easy-install.sh -> src/gl-easy-install
        src/99-emergency-addkey.sh -> src/gl-emergency-addkey
        src/install.pl -> src/gl-install
        src/update-hook.pl -> src/hooks/update
    Sitaram Chamarty committed Nov 13, 2009
  2. Merge branch 'gitweb-descriptions'

    Sitaram Chamarty committed Nov 13, 2009
Commits on Nov 12, 2009
  1. compile: writing description file should be conditional

    Sitaram Chamarty committed Nov 12, 2009
  2. doc/2: add docs for gitweb description, plus some minor cleanup

    Sitaram Chamarty committed Nov 12, 2009
  3. compile: added repo descriptions

    example line in config file:
    
    gitolite = "fast, secure, access control for git in a corporate environment"
    Sitaram Chamarty committed Nov 12, 2009
  4. doc/6: added two keys explanation and workaround

    Sitaram Chamarty committed with Sitaram Chamarty Nov 12, 2009
Commits on Nov 7, 2009
  1. new program for emergency addkey; run without args for usage

    Sitaram Chamarty committed Nov 7, 2009
Commits on Nov 6, 2009
  1. (please read full commit message) upgrade behaviour changed

        **upgrades no longer touch the config or the keydir**
    
    When you first install gitolite, the easy install script has to do two
    *distinct* things:
    
      * install the software
      * create and seed the gitolite-admin repo with a minimum config file
        and the newly created pubkey
    
    That's fine for an install, because nothing exists yet anyway.
    
    Subsequent invocations of the script should only do the first task (so
    that gitolite itself can be upgraded), and not attempt to fiddle with
    the config file and pubkeys.
    
    Unfortunately, until now I had not been separating these two activities
    cleanly enough.  For instance, the commit message for 8e47e01 said:
    
        IMPORTANT: we assume that $admin_name remains the same in an upgrade
        -- that's how we detect it is an upgrade!  Change that name or his
        pubkey, and you're toast!
    
    Ouch!
    
    So now I decided to clean things up.  The "Usage" message tells you
    clearly what to do for an upgrade.
    
    Should have been like this from the beginning, but hey we got there
    eventually :)
    
    ----
    
    Code-wise, this is a major refactor of the easy install script.  It uses
    an old forgotten trick to get forward refs for bash functions ;-) and in
    the process cleans up the flow quite a bit.
    Sitaram Chamarty committed Nov 6, 2009
  2. easy install: handle upgrades specially

      - "it's an upgrade" is decided by presence of gitolite.conf (not a pubkey)
      - admin_name optional (and will be ignored if given) for upgrades
    
    plus a lot of comments and some minor text changes
    Sitaram Chamarty committed with Sitaram Chamarty Nov 5, 2009
Commits on Nov 5, 2009
  1. compile: death should be a little louder and clearer :)

    Sitaram Chamarty committed Nov 3, 2009
  2. doc/6: rename the file, change focus completely

    Sitaram Chamarty committed with Sitaram Chamarty Nov 3, 2009
  3. doc/1: fix formatting problem on github

    (local mkd worked fine... weird!)
    Sitaram Chamarty committed with Sitaram Chamarty Nov 5, 2009
Commits on Oct 30, 2009
  1. doc/src: major doc/help text revamp

    also removed some dead code from compile (pre PTA days)
    Sitaram Chamarty committed Oct 30, 2009
  2. Merge branch 'gh-issue-2' into pu

    Sitaram Chamarty committed Oct 30, 2009
  3. easy install: clean up after yourself :)

    Sitaram Chamarty committed Oct 30, 2009
  4. doc/6: explain that all this is *only* for the admin

    Sitaram Chamarty committed Oct 30, 2009
  5. compile: (gh issue 2) apparently pubkeys don't always end in a newline

    I've never encountered this but it's an easy fix
    Sitaram Chamarty committed Oct 23, 2009
  6. auth: make ".git" at the end optional

    Sitaram Chamarty committed with Sitaram Chamarty Oct 29, 2009
  7. easy install: cleaned up the closing credits; err I mean instructions :)

    Sitaram Chamarty committed with Sitaram Chamarty Oct 29, 2009
Commits on Oct 28, 2009
  1. auth, doc/3: print useful information when no command given

    Sitaram Chamarty committed with Sitaram Chamarty Oct 28, 2009
  2. easy install: save version info, print upgrading message

    Sitaram Chamarty committed with Sitaram Chamarty Oct 28, 2009
  3. doc/3: add section on unexpected gitwebauth good-ness!

    Sitaram Chamarty committed with Sitaram Chamarty Oct 27, 2009
Something went wrong with that request. Please try again.