If you read my last article about setting up your own GitBlit Server with Domino credentials this is the next step. Creating your first repository and pushing up an xpage application to the server.
Login to your git blit server and click on the repositories tab
Click on new Repository at the right hand side of the UI
Give your new repository a name, and write a description if you like.
There is lot’s of other options that you can setup but they are not needed for this example.
Click on the access permission tab
Add owners to the repository, change the access restrictions so your users can view, clone and push.
Also change the authorization control for the users. Now your repository is ready to be saved, so Click on Save.
When the repository is saved, it’s time to get the Repository URL that we need to clone the repository.
Click on your prefered git client software, my prefered client is SourceTree
Copy this URL into your application and clone the repository.
And you are ready to get the most out of your development.
Today I’m going to show you hav to setup you own internal Free Git server in five minutes
Make sure that you have java version 7 installed in you windows server. JRE or JDK any version works. If you don’t have one goto java.com and install the a java jre.
Goto the java download page scroll down to the bottom of the page and download the JCE
Open up the downloaded zip file and copy the 2 selected files
To the folder lib\security below your java installation folder in my case it was
C:\Program Files\Java\jre7\lib\security you might need to replace existing files nothing to worry about.
This is needed to be able to create the certificates later.
Next step is to gitblit.com wher your download the Go Git Blit Server for Windows or if you are using Linux or Macosx use that version.
Unzip the zip file in the root to a folder called gitblit or a suitable sub folder, if you change the folder you might need to change url:s in the .cmd files.
Configure GitBlit
We are now going to configure gitblit to use LDAP as authentication method
Open up the file gitblit.properties in the data folder, search for the keyword realm.userService edit this line so the line should look like this realm.userService = com.gitblit.LdapUserService
Setup the connection to the LDAP server
realm.ldap.server=ldap://localhost change the row if your LDAP server isn’t on localhost remember if you want to connect to a domino server and it’s hosted on a windows machine that has AD LDAP on it you need to change the port for the Domino LDAP service.
The syntax if you want to change ip or port is like this ldap://192.168.10.10:399
You also need to change the login user to be able to use the domino LDAP Service
realm.ldap.admins can be edited to add a admin group from LDAP
change the row realm.ldap.email from email to mail
And the row realm.ldap.uid also to mail
Important last step, search the file for localhost and remove that otherwise gitblit will only operate on localhost and you can access it from another machine
Save the file
Generate SSL Certificate
In the Gitblit folder in my case c:\GitBlit there is a cmd file called authority.cmd (if you have another url you might need to modify the file)
start authority.cmd add the information about your certificate
Write the password for your keystore, write gitblit if you don’t want that password you need to edit the gitblit config file so the password match.
The keystore is generated and the cert admin is opened
Close the Window
Start the Git Blit Server using the gitblit.cmd the server will now start in the window.
Your Git server should be up and running now. Let’s access it thru a browser.
Write https://servername or ipadress or localhost and end the adress with :8443
but if you want to use http instead you need to edit the gitblit.properties and change the row
server.httpPort =0 to have the port for the http server i.e. server.httpPort = 8080
The GitBlit interface will load.
Try to login using your Domino credentials
When you have logged in, logout again and login using the standard admin user
username: admin password: admin
and assign yourself as an administrator and change the password of the default admin
Login with your user again
Now your ready to create your first repository
Next step is to connect your git client to the repository. Some clients like sourcetree needs a special setup to accept ssl that is created using a self cert. But that is for the next post.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.