This is much faster version of redmine-gitosis plugin, which has no issues with long administrative logins on trackers with huge amount of repos.
Also, I get rid of file locks, which is lame, if you using distributed VCS and added ability to manage externals repos, using gitosis-external.
This version is tested with our redmine installation and have no known issues.
Super fast version of gitosis-redmine plugin. Initial version
Removing empty writer class
Some readme changes
Extra folder is no longer needed
Do not preform anything, if gitosis repo url is not configured
Typo in permissions fixed
Should be size instead of keys :(
Observer now using redmine plugin settings, instead of lame infile co…
Update path to new Gitosis.repos_path
Btw, it supports read/write access permissions, and after little patching you will be able to destroy existent keys.
Edited README.rdoc via GitHub
Any comments? I just wondering why this pull request still not merged.
Hello? Why is this pull request still not merged?
Project seems dead. I have no Ruby skills, so I just used the more updated https://github.com/xdissent/redmine_gitosis .
Which version of this plugin are you using with latest Redmine releases? Is anyone willing to maintain this plugin? O:-)
https://github.com/ericpaulbishop/redmine_git_hosting seems to be the most actively developped version with the greatest (community) participation of all forks
@sebix oh my. All redmine-gitosis forks share same crappy logic to fetch projects from database. This will cause HUGE performance issues on huge redmine installations (hundreds of projects and repos, tens of users), since redmine touches updated_at on login, and it trigger gitosis plugin callbacks, and it updates repo.
And they also use this fucking file locking. For real! File locking in web applications, which manage distributed VCS. Pathetic.
@y8 is your fork compatible with existing installations of the original plugin? I'm using the xdissent fork, but seems abandoned and I'm attracted by the fact you improved its performance (although I didn't test it by myself yet).
Do you plan to maintain it? It would be great!
@adobo almost. There few little changes in configuration, but all other stuff is pretty same.
I should add ability to remove existent keys, since all externals keys will be placed in external folder and there no need to maintain unused keys.
I don't know about writing code for this plugin, but I can find time to maintain and review pull requests.