This is an old revision of the document!
This explains how you can configure Git Winch to suit your requirements.
Firstly we assume you have installed Git Winch after reading the installation instructions here.
The following files in the application folder; can be configured by you. If you are the owner/manager of your office, you can zip up the same application folder and give the zip file to your own staff; so that they don't have to spend time configuring Git Winch.
File that can be edited:
The above HTML files can be edited using your favourite HTML editor and/or text editor as per your liking. However, you should NOT use Javascript in them. Git Winch does have a simple HTML viewer but that does not have capability to execute Javascript. It also does not support some parts of CSS and some advanced HTML.
ORGNAME
The orgname.txt is used to set a name for your office (or the division in the office where Git Winch is being used) The first 10 characters are only used. By default it is “ASOS” (Why? For historical reasons which we need not go into here) You will see the orgname at the bottom of the window inside Git Winch.
config.txt
This has 3 lines in it. Each line is a <name>=<value> You need to change the value of only the line where you (as an owner) are hosting your Repository files in your office. After making suitable changes, you need to make sure all your staff gets this file else Git Winch will not work for them.
gitwinch.ini
This file contains various specialized configuration that are needed for Git Winch to work properly. This is an important file, so it is explained separately here.