deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
Hosting git repositories -- Gitolite allows you to setup git hosting on a central server, with very fine-grained access control and many (many!) more powerful features.
201 commits 6 branches 50 tags 2.8 MiB
Perl 88.8%
Shell 10.3%
Public Key 0.8%
Raku 0.1%
Find a file
Sitaram Chamarty 198dcfd4c8 POST_CREATE efficiency... (please read below if you care) 
The POST_CREATE trigger is called when

  * a user creates a new "wild" repo,
  * a user uses the "perms" command, and
  * a user uses the "fork" command.

The trigger calls 3 programs (see rc file):

    post-compile/update-git-configs
    post-compile/update-gitweb-access-list
    post-compile/update-git-daemon-access-list

(They are also called by the POST_COMPILE trigger, by the way.)

However, the 3 programs shown are a bit wasteful -- they run through
*all* the repos when really only *one* repo has been affected.

This patch

  * passes the repo name to the 3 programs (duh!)

  * adds the optimisation to the first of the 3 programs listed above
    (the one dealing with 'git config').

For the other two programs (gitweb and git-daemon), you have 3 choices:

  * if you don't have too many repos, ignore the problem.

  * take out the 2nd and 3rd lines from the POST_CREATE list in the rc
    file, so they don't run.

    Then run 'gitolite trigger POST_COMPILE' from cron at regular
    intervals.  (Note that is POST_COMPILE not POST_CREATE!)  However,
    this means that gitweb and daemon permissions won't be current
    immediately after someone adds a new repo or sets perms etc.; they
    get updated only on the next cron run.

  * patch the programs to add this optimisation (and send me the
    patches).  The optimisation would check if arg-1 ($1 in shell,
    $ARGV[0] in perl) is 'POST_CREATE', and if it is, take the *next*
    argument as a repo name that may have changed.
2012-04-22 22:44:39 +05:30
doc fork command, and some core changes to make it work... 2012-04-22 16:56:21 +05:30
src POST_CREATE efficiency... (please read below if you care) 2012-04-22 22:44:39 +05:30
t fork command, and some core changes to make it work... 2012-04-22 16:56:21 +05:30
check-g2-compat (some minor changes) 2012-04-05 21:31:59 +05:30
convert-gitosis-conf (mostly) doc changes 2012-04-10 15:41:32 +05:30
dot.pl Q: all doc stuff 2012-03-24 18:22:11 +05:30
install install should fail more gracefully if the '-ln' directory does not exist 2012-04-22 22:43:27 +05:30
README.mkd (some docfixes) 2012-04-21 22:29:56 +05:30

README.mkd

Gitolite README

Github users: please read the "wiki" link at the top of the page before submitting issues or pull requests.

If you're reading this on the main gitolite page on github, several IMPORTANT CHANGES have happened to gitolite:

  1. A competely re-written version of gitolite has been pushed to the "master" branch, and is now the actively maintained and supported software. Do NOT try to merge this with your old "master" branch!

    The main page leads to several useful starting points. The table of contents is a much more meaningfully ordered/structured list of links (instead of putting them in alphabetical order of the filename, like in g2!)

    If you are an existing (g2) user and wish to migrate, you MUST read this.

  2. Versions v2.x are on branch "g2". It will be supported for security issues and serious bugs in core functionality, but not for anything less critical. Versions v1.x are completely unsupported now. (Documentation links for this version are here and here).

License information for code and documentation is at the end of doc/index.mkd (or you can read it online here).