Changes between Version 5 and Version 6 of Give users access to gitolite repos
- Timestamp:
- 04/30/25 08:54:27 (3 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Give users access to gitolite repos
v5 v6 1 == Create a new SSH key pair for every user or role 1 == Give users access to gitolite repos 2 3 All changes to your running gitolite instance are made on the checked out gitolite-admin repo. 4 They come into effect as soon as you push them to the server 5 6 === Create a new SSH key pair for every user or role 2 7 3 8 {{{#!sh … … 18 23 19 24 20 == Add the new public key to Gitolite25 === Add the new public key to Gitolite 21 26 22 === Clone the gitolite-admin repo if you haven't already:27 ==== Clone the gitolite-admin repo if you haven't already: 23 28 24 29 {{{#!sh … … 26 31 }}} 27 32 28 === Copy the user key to the keydir33 ==== Copy the user key to the keydir 29 34 30 35 {{{#!sh … … 33 38 }}} 34 39 35 == Edit conf/gitolite.conf40 === Edit conf/gitolite.conf 36 41 {{{ 37 42 repo airsituation … … 49 54 '''mesepackager''' can '''only read''' the '''airsituation''' repo 50 55 51 == Push changes to effect your setup56 === Push changes to effect your setup 52 57 53 58 Once you changed keydir/ and/or conf/, you must commit and push like this: … … 61 66 After push, Gitolite applies changes automatically — no restart needed. 62 67 63 == Edit local ~/.ssh/config68 === Edit local ~/.ssh/config 64 69 65 70 Host kokyou.dev … … 82 87 SSH knows which key to use depending on which Host alias you reference. 83 88 84 == Push an existing local project to Gitolite89 === Push an existing local project to Gitolite 85 90 86 91 From your project directory: … … 98 103 }}} 99 104 100 == Clone a repo using different users/keys105 === Clone a repo using different users/keys 101 106 102 107 Example:
