- Install
- Authentication Providers
- Membership Services
- Frequently Asked Questions
- fatal: http: /info/refs not valid: is this a git repository?
- Bonobo Git Server doesn’t serve CSS
- Cloning Error — RPC failed
- SSL and large repositories
- Error 500.19 and file execution issues and locked on IIS 8
- Saved searches
- Use saved searches to filter your results more quickly
- License
- xfherui/Bonobo-Git-Server
- Name already in use
- Sign In Required
- Launching GitHub Desktop
- Launching GitHub Desktop
- Launching Xcode
- Launching Visual Studio Code
- Latest commit
- Git stats
- Files
- readme.md
- Saved searches
- Use saved searches to filter your results more quickly
- jakubgarfield/Bonobo-Git-Server-Web
- Name already in use
- Sign In Required
- Launching GitHub Desktop
- Launching GitHub Desktop
- Launching Xcode
- Launching Visual Studio Code
- Latest commit
- Git stats
- Files
- README.md
Install
This page covers simple Bonobo Git Server installation. Be sure to check prerequisites page before installation and for other sections visit the documentation page.
The following steps covers an installation with Windows 2008 Server and IIS 7. They are exactly the same for any higher platforms (Windows Server 2012 and IIS 8.0+).
- Download the latest version of Bonobo Git Server from the front page
- Extract the files from the installation archive to C:\inetpub\wwwroot
- Allow IIS User to modify C:\inetpub\wwwroot\Bonobo.Git.Server\App_Data folder. To do so
- select Properties of App_Data folder,
- go to Security tab,
- click edit,
- select IIS user (in my case IIS_IUSRS) and add Modify and Write permission,
- confirm these settings with Apply button.
- Convert Bonobo.Git.Server to Application in IIS
- Run IIS Manager and navigate to Sites -> Default Web Site. You should see Bonobo.Git.Server.
- Right click on Bonobo Git Server and convert to application.
- Check if the selected application pool runs on .NET 4.0 and convert the site.
Enable Anonymous Authentication in IIS and disable the others. To do so, select the application, click on the authentication icon and set the value to of Anonymous Authentication to Enabled. The configuration should look like the following screenshot.
- Launch your browser and go to http://localhost/Bonobo.Git.Server. Now you can see the initial page of Bonobo Git Server and everything is working.
- Default credentials are username: admin password: admin
The authentication and membership service functions have been split up into separate configurable modules in the latest version of Bonobo Git Server. By default, it is configured to use Cookie Authentication and the Internal Membership Service. Please follow up on how to use the different methods using the following sites.
Authentication Providers
Membership Services
If you are have a previous version installed, you should review these migration notes.
If you have any issues with the installation try to search FAQ and forum.
Frequently Asked Questions
For allowing anonymous push you have to modify global settings.
- Log in as an administrator.
- Go to Global Settings.
- Check the value Allow push for anonymous repositories
- Save changes.
fatal: http: /info/refs not valid: is this a git repository?
This is a git client way of saying that it didn’t receive git stream as a response from a server. That usually means, that there has been an error on the server side.
To determine what type of error it is, view the log file located at App_Data/Bonobo.Git.Server.Errors.log .
Bonobo Git Server doesn’t serve CSS
This is a common issue for Windows 8 users, please see the topic. The solution is simple:
- Go to Turn windows features on or off screen
- Navigate IS -> WWWS -> Common HTTP Features
- Tick Static Content
Cloning Error — RPC failed
There are multiple reasons why this error can occure on the client, but the most frequent ones are related to the size of the request. If you encounter this issue try to increase the following values.
- run git config http.postBuffer [desired size] on your client, you can try 524288000
- increase in web.config; the size could be 1073741824
- increase in web.config; try the value 1024000
Apparently, there is no need in limiting maxRequestLength on IIS 8.0 so if you run into troubles, try to remove the line.
SSL and large repositories
When using SSL and pushing large repository you should increase the variable size as described above and if it still doesn’t help you should apply the following Microsoft patch (KB2634328).
Error 500.19 and file execution issues and locked on IIS 8
To resolve it I had to execute:
%windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/handlers %windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/modules
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
License
xfherui/Bonobo-Git-Server
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
readme.md
Thank you for downloading Bonobo Git Server. For more information please visit http://bonobogitserver.com.
- Internet Information Services 7 and higher
- How to Install IIS 8 on Windows 8
- Installing IIS 8 on Windows Server 2012
- Installing IIS 7 on Windows Server 2008 or Windows Server 2008 R2
- Installing IIS 7 on Windows Vista and Windows 7
- Windows Vista SP2, Windows 7, Windows 8 and higher
- Windows Server 2008 R2, Windows Server 2008 SP2, Windows Server 2012 and higher
- Don’t forget to register .NET framework with your IIS
- Run %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir with administrator privileges
Before each update please read carefully the information about compatibility issues between your version and the latest one in changelog.
- Delete all the files in the installation folder except App_Data.
- Default location is C:\inetpub\wwwroot\Bonobo.Git.Server .
These steps illustrate simple installation with Windows 2008 Server and IIS 7. They are exactly the same for higher platforms (Windows Server 2012 and IIS 8.0).
- Extract the files from the installation archive to C:\inetpub\wwwroot
- Allow IIS User to modify C:\inetpub\wwwroot\Bonobo.Git.Server\App_Data folder. To do so
- select Properties of App_Data folder,
- go to Security tab,
- click edit,
- select IIS user (in my case IIS_IUSRS) and add Modify and Write permission,
- confirm these settings with Apply button.
- Run IIS Manager and navigate to Sites -> Default Web Site. You should see Bonobo.Git.Server.
- Right click on Bonobo Git Server and convert to application.
- Check if the selected application pool runs on .NET 4.0 and convert the site.
- Default credentials are username: admin password: admin
Frequently Asked Questions
How to clone a repository?
- Go to the Repository Detail.
- Copy the value in the Git Repository Location.
- It should look like http://servername/projectname.git .
How do I change my password?
- Click on the account settings in the top right corner.
- Enter new password and confirmation.
- Save.
- Go to the installation folder of Bonobo Git Server on the server.
- Default location is C:\inetpub\wwwroot\Bonobo.Git.Server .
How to change repositories folder?
- Log in as an administrator.
- Go to Global Settings.
- Set the desired value for the Repository Directory.
- Directory must exist on the hard drive.
- IIS User must have proper permissions to modify the folder.
Can I allow anonymous access to a repository?
- Edit the desired repository (or do this when creating the repository).
- Check Anonymous check box.
- Save.
For allowing anonymous push you have to modify global settings.
- Log in as an administrator.
- Go to Global Settings.
- Check the value Allow push for anonymous repositories
- Save changes.
I’d like to use git hooks to restrict access. How do I access the web frontend usernam?
Bonobo provides the following environment variables:
- AUTH_USER : The username used to login. Empty if it was an anonymous operation (clone/push/pull)
- REMOTE_USER : Same as AUTH_USER
- AUTH_USER_TEAMS : A comma-separated list containing all the teams the user belongs to. Commas in teams name are escaped with a backslash. Backslashes are also escaped with a \ . Example: Teams ‘Editors\ Architects’, ‘Programmers,Testers’ will become Editors\\ Architects,Programmers\,Testers .
- AUTH_USER_ROLES : A comma-separated list containing all the roles the user belongs to. Commas in roles are escaped with a backslash. Backslashes are also escaped with a \ .
- AUTH_USER_DISPLAYNAME : Given Name + Surname if available. Else the username.
Beware that due to the way HTTP basic authentication works, if anonymous operations (push/pull) are enabled the variables above will always be empty!
- update changelog
- update version numbers in appveyor.yml
- add tag so it appears under releases with git tag -a 6.0.0 -m «Release 6.0.0»
- add zipped version to bonobogitserver.com at Bonobo-Git-Server-Web
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
jakubgarfield/Bonobo-Git-Server-Web
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
The site uses nanoc — a static site generator — to convert a few md pages into html. It is also powered by github pages.
There is a master branch with the source code that gets converted with nanoc into output directory and the result is pushed into a gh-pages branch on the same repository.
So you have the following structure:
/Bonobo-Git-Server/ # folder pointed to master branch with sources /Bonobo-Git-Server/output # generated folder by nanoc that points to git gh-pages branch
You need to have a ruby installed — version 2.2.6. For Windows use RubyInstaller. For UNIX I recommend using rbenv and ruby-build.
After checking that ruby is installed and the version matches with ruby -v install bundler.
Next thing is cloning the project and it’s gh-pages branch.
git clone https://github.com/jakubgarfield/Bonobo-Git-Server-Web.git cd Bonobo-Git-Server-Web git clone --depth 1 https://github.com/jakubgarfield/Bonobo-Git-Server-Web.git -b "gh-pages" output
In ruby the dependencies are called ruby gems (stored in Gemfile) and installed with bundler. In the project directory run the following:
bundle install # installs dependencies bundle exec nanoc # starts nanoc compilation bundle exec nanoc view # starts localhost:3000 server to check the result
Every time you make a change run bundle exec nanoc to compile it to the output and if you run bundle exec nanoc view (you can keep it running in another terminal window) you can browse http://localhost:3000 to check the website.
- add the new zipped version to content/resources/releases/
- change content/index.erb to point to the new version
- update content/changelog.md to reflect the new release
After that you can run . deploy.sh «Release X.X.X» to publish the changes if you are on UNIX machine or publish to gh-pages branch manually.
# commit changes to master branch git add . git commit -m "Release X.X.X" git push origin master # compile the site and remove obsolete files bundle exec nanoc bundle exec nanoc prune --yes # publish to github pages cd output git add . git commit - m "Release X.X.X" git push origin gh-pages