-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New v1 install not creating repos #342
Comments
Tried also on a fresh bootstrapped wheezy following this howto with same result - logs are fine but no repos are installed. |
|
I don't use Passenger. I find the installation a bit complicated. I prefere Puma. |
oliwel, look at this - http://stackoverflow.com/questions/22255742/getting-ruggednetworkerror-on-connect (you have error with gitolite-rugged compilling - missing libssl-dev ) |
@oliwel Any news? |
Well, I dont see much help towards the problem here - the base system works and as redmine does at users to the gitolite I assume that the connector is working. What about the difference in the "class name"? Is this intended or a bug? |
Can you please send me them to [email protected]? |
Can I close it? :) |
I hope so - I need some time to migrate my prod systems but I can reopen the ticket if the problem persists. Might you post the solution here for Follow Ups? |
Enable Xitolite repositories in Administration -> Settings -> Repositories |
I setup a new fresh install using the v1.0 plugin on ruby2.1.5 - the UI integration seems to work, the config test page is all green. User keys are added to gitolite but no repos are created nor listed in the config.
Compared to a migrated install (which also does not work!) I still see "Redmine:Git" as class name in the repositories table.
I dont know what am I doing wrong as my installs always need a lot of tweaking till they work - what distribution with what ruby/rails versions can you recommend?
The text was updated successfully, but these errors were encountered: