summaryrefslogtreecommitdiff
path: root/doc/forum/integration_with_gitolite.mdwn
diff options
context:
space:
mode:
authordavid@1439a1cab13195a56248b6a8fd98a62028bcba8a2018-08-23 01:14:26 +0000
committeradmin2018-08-23 01:14:26 +0000
commit9bb7d0ac997995e5d83843b3331258ee8e0fa32d (patch)
tree62da6177145a3557d6ae5d31d574509215b191e3 /doc/forum/integration_with_gitolite.mdwn
parent9c90f6c98b312d7108a356e618412b0b7ae2783f (diff)
Diffstat (limited to 'doc/forum/integration_with_gitolite.mdwn')
-rw-r--r--doc/forum/integration_with_gitolite.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/forum/integration_with_gitolite.mdwn b/doc/forum/integration_with_gitolite.mdwn
new file mode 100644
index 00000000..956d35c3
--- /dev/null
+++ b/doc/forum/integration_with_gitolite.mdwn
@@ -0,0 +1,2 @@
+Does anyone have any experience with integrating propellor and gitolite? I'd be happy with just ssh pubkey management.
+There seem to be two main options. The typical way of managing a gitolite site is by pushing a special git repository "gitolite-admin". There are also a script called [ukm](http://gitolite.com/gitolite/ukm.html). I'm not sure what will be the least hassle. Currently I have to manually commit and push various keys (including the keys needed for access to the propellor repos). Part of the problem could be solved by making the propellor repos available anonymously, but I still have my own ssh key(s) to manage.