Ok so given that no one responded I assume that either no one has done this or perhaps I didn't explain myself correctly. At any rate I started trying to do this myself.
First of all I already have one working version of gitrorious install and using the standard user of git. In order to get another one working I assumed that I need a different user running it so this is what I have done. I have the git user and I have made a repo user. I also made a gitorious group that both users belong to. I installed gitorious into the standard /var/www/gitorious location and have given the gitorious group rwx permissions on all files. I have edited the gitorious.yml file and added a production.repo environment. I have also added a production.repo.rb under the environments dir and added a production.repo entry to the broker.yml file that has a single adapter: stomp line. I am using thin to run my instances under the git user i run thin -e production -d start. Under the repo user I run thin -e production.repo -p 3030 -P tmp/pids/thin.repo.pid -d start. The instance running under git works perfectly. The instance running under repo starts up without errors when I browse to the url it shows perfectly however when I try to add an ssh key it adds it but is never ready. When I look at the authorized_keys file of repo there is nothing there however the key is added to the authorized_keys file for the git user. I suspect that is why the key never shows up as ready. If I try to add a repository it just fails completely, I get the something went wrong page. I suspect I am getting really close to getting the setup working I just need a little more guidance if anyone has it. If anyone could help I would greatly appreciate it. Regards, JD
-- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
