User Tools

Site Tools


pld-gitolite

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
pld-gitolite [2012-04-04 22:02]
draenog [Package deletion]
pld-gitolite [2012-06-20 08:29]
glen add link to changes to developer page
Line 18: Line 18:
 Authentication is based on ssh keys. People whose keys are in SSH-keys in PLD repository should have access. Authentication is based on ssh keys. People whose keys are in SSH-keys in PLD repository should have access.
  
 +===== Changes to Developer =====
 +
 +Changes to developer can be seen from [[cvs2git]] page.
 ===== Access control===== ===== Access control=====
 ==== Assumptions:​ ==== ==== Assumptions:​ ====
Line 52: Line 55:
  
 ===== New package creation ===== ===== New package creation =====
-In upstream version of gitolite, new package is created by cloning of no existing repo (if the access rules allow for it). However I think that it is too error prone. So [[https://​github.com/​draenog/​gitolite|gitolite was forked]] and an option to disable creation of wildcard repositories was added. Instead an [[http://​sitaramc.github.com/​gitolite/​doc/​admin-defined-commands.html|admin defined command]] was created for this task:+In upstream version of gitolite, new package is created by cloning of no existing repo (if the access rules allow for it). However I think that it is too error prone. So [[https://​github.com/​draenog/​gitolite|gitolite was forked]] and an option to disable creation of wildcard repositories was added. Instead an [[http://​sitaramc.github.com/​gitolite/​ADCs.html|admin defined command]] was created for this task:
   ssh draenog@carme.pld-linux.org create <​new_repo>​   ssh draenog@carme.pld-linux.org create <​new_repo>​
  
pld-gitolite.txt ยท Last modified: 2016-03-21 10:20 by glen