Changes between Version 11 and Version 12 of TracGitosisPlugin
- Timestamp:
- Jul 23, 2015, 2:29:08 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracGitosisPlugin
v11 v12 1 1 [[PageOutline(2-5,Contents,pullout)]] 2 2 3 = Gitosis administration plugin =3 = Gitosis administration plugin 4 4 5 == Description ==5 == Description 6 6 7 This plugin allows partial gitosis administration from Trac. 7 This plugin allows partial gitosis administration from Trac. Users will be able to add their public SSH key in gitosis in a new settings tab. 8 8 9 Users will be able to add their public SSH key in gitosis (new settings tab).9 Admins will be able to set the location of the gitosis-admin repository and settings for the git repository associated with Trac (requires GitPlugin). 10 10 11 Admins will be able to set the location of the gitosis-admin repository and settings for the git repository associated with Trac (requires GitPlugin.) 12 13 == Bugs/Feature Requests == 11 == Bugs/Feature Requests 14 12 15 13 Existing bugs and feature requests for TracGitosisPlugin are … … 17 15 18 16 If you have any issues, create a 19 [ http://trac-hacks.org/newticket?component=TracGitosisPlugin&owner=dr4Kenew ticket].17 [/newticket?component=TracGitosisPlugin new ticket]. 20 18 21 == Download == 19 [[TicketQuery(component=TracGitosisPlugin&group=type,format=progress)]] 20 21 == Download 22 22 23 23 Download the zipped source from [https://github.com/dr4Ke/TracGitosisPlugin/archive/latest.zip GitHub]. 24 24 25 == Source ==25 == Source 26 26 27 27 You can check out TracGitosisPlugin using {{{git clone git://github.com/dr4Ke/TracGitosisPlugin.git}}}, or [http://github.com/dr4Ke/TracGitosisPlugin browse the source] on !GitHub. 28 28 29 == Configuration ==29 == Configuration 30 30 31 Before this plugin can work, you need a few things 31 Before this plugin can work, you need a few things: 32 32 - a working git installation on the server running Trac 33 33 - SSH key pair without passphrase for the user running Trac 34 34 - access to a gitosis-admin repository 35 35 36 === SSH key pair === 36 === SSH key pair 37 37 38 Example on a RHEL server using Apache httpd : 38 {{{ 39 #!sh 39 {{{#!sh 40 40 # Create the key pair without passphrase 41 41 mkdir /var/www/.ssh … … 47 47 }}} 48 48 49 === Configure access to gitosis-admin ===49 === Configure access to gitosis-admin 50 50 51 51 Simply add the previously generated public key in the file {{{keydir/trac.pub}}} and add the user {{{trac}}} in the {{{gitosis-admin}}} group members in the {{{gitosis.conf}}} file as for a standard gitosis admin. Then commit and push your changes. That should do it. 52 52 53 == Configuration into Trac ==53 == Configuration into Trac 54 54 55 55 You have to enable the plugin (and restart Trac) with this parameter in {{{trac.ini}}}: 56 {{{ 57 #!ini 56 {{{#!ini 58 57 [components] 59 58 tracgitosis.* = enabled 60 59 }}} 61 Next, in the Admin panel, you'll see Two new pages in a new {{{Trac Gitosis}}} section: 60 61 Next, in the Admin panel, you'll see two pages in a new {{{Trac Gitosis}}} section: 62 62 - Admin Settings 63 63 - Repository Settings 64 64 65 In the {{{Admin Settings}}}, you must give gitosis-admin access parameters before you can really use this plugin:65 In the {{{Admin Settings}}}, you must give gitosis-admin access parameters before you can actually use this plugin: 66 66 ||Parameter||Default value||Description|| 67 67 ||Admin Repository Name||gitosis-admin||the name of the gitosis administration special repository|| … … 71 71 Save changes and enjoy the {{{Repository Settings}}} (for admins only) and the {{{gitosis SSH public key}}} in all users preferences. 72 72 73 == How it works ==73 == Usage 74 74 75 75 When accessing either {{{Repository Settings}}} or {{{gitosis SSH public key}}} for the first time, Trac clones the gitosis-admin repository at the root of the trac project. 76 76 77 Then, each time these pages are displayed, the repository is pulled in order to read current settings and public keys. When you press {{{Save changes}}}, the repository is pulled again, settings are written into {{{gitosis.conf}}}, public key is written into {{{keydir/<user>.pub}}}, changes are commit ed and pushed to the main admin repository.77 Then, each time these pages are displayed, the repository is pulled in order to read current settings and public keys. When you press {{{Save changes}}}, the repository is pulled again, settings are written into {{{gitosis.conf}}}, public key is written into {{{keydir/<user>.pub}}}, changes are committed and pushed to the main admin repository. 78 78 79 == Warning == 80 The gitosis file is overwritten each time setting are saved in Trac using a modified !ConfigParser python class. The [gitosis] section will be written first. All other sections will be written in a sorted way. In each section, the parameters are written the same sorted way. 79 '''Warning''' 80 81 The gitosis file is overwritten each time setting are saved in Trac using a modified !ConfigParser Python class. The [gitosis] section will be written first. All other sections will be written in a sorted way. In each section, the parameters are written the same sorted way. 81 82 82 83 In short, this means: 83 84 - sections and parameters will be moved if they were not sorted in the original file 84 - all comments will be lost (because I don't know were to write them after section and/or parameters moved)85 - all comments will be lost, because I don't know were to write them after section and/or parameters moved 85 86 86 == Recent Changes ==87 == Recent Changes 87 88 88 89 See [http://github.com/dr4Ke/TracGitosisPlugin/commits/master GitHub history] 89 90 90 == Author/Contributors ==91 == Author/Contributors 91 92 92 93 '''Author:''' [wiki:dr4Ke] [[BR]] 93 '''Maintainer:''' [ wiki:dr4Ke] [[BR]]94 '''Maintainer:''' [[Maintainer]] [[BR]] 94 95 '''Contributors:'''
