Git Winch Guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
installation [2025/06/13 04:11] – admininstallation [2025/06/13 04:31] (current) – admin
Line 7: Line 7:
 **CRITICAL**: The folder that it is installed into should be //writable//!   **CRITICAL**: The folder that it is installed into should be //writable//!  
  
-**Pre-requisites**\\ +====Pre-requisites====
-//Git Winch// works ONLY on Windows. So the entire office that uses //Git Winch// must be using Windows. (We may release Linux and Mac versions later, if there is serious demand) Such computers MUST have //Chrome// browser installed at its default location in the computer.+
  
-The first time you start //Git Winch// it will start Chrome browser in //app// mode. That startup will result in over 100Mb (approx) of files needed by Chrome in a sub-folder inside the application folder. That is a normal activity and so you don't have to get worried.+//Git Winch// works ONLY on Windows. So the entire office that uses //Git Winch// must be using Windows. (We may release Linux and Mac versions later, if there is serious demand) 
  
-There are several files after installation that you should definitely NOT delete or touch. However there are a few that can be configured specifically for your office. This is explained [[configuration?do=export_xhtml|here]]. Once you configure //Git Winch// specifically for your office, you can also zip up the application folder and distribute that to your own office workers.+**//Chrome (or a browser similar to Chrome) is needed!//**\\ 
 +Your computer MUST have //Chrome// browser installed at its default location in the computer. You can also use browser such as //Brave, Edge and Chromium// too. But those would need the //gitwinch.ini// file to be changed ...//explained later as you read below//. 
 + 
 +The first time you start //Git Winch// it will start Chrome browser in //app// mode. That startup will result in over 100Mb (approx) of files needed by Chrome in a sub-folder inside the application folder. That is a normal activity and so you don't have to get worried.
  
 +**//Git is needed!//**\\
 You also need to install //Git// To check if you have that utility installed, please open a command-line window (console window or "cmd" window) and just give this command:  You also need to install //Git// To check if you have that utility installed, please open a command-line window (console window or "cmd" window) and just give this command: 
  
Line 20: Line 23:
 If you see the version number in the output, that means Git has been installed. If not, you should download Git installer and install it https://git-scm.com/downloads/win and do the above check again. If you see the version number in the output, that means Git has been installed. If not, you should download Git installer and install it https://git-scm.com/downloads/win and do the above check again.
  
 +**//Curl is needed!//**\\
 You should also check if the //curl// command is working globally on your computer. Again, you should open a cmd window and give this command: You should also check if the //curl// command is working globally on your computer. Again, you should open a cmd window and give this command:
    
Line 29: Line 33:
 You MUST set a suitable organization/division code for yourself. This is a simple text written in a text file named //"orgname.txt"// which must be kept in the same folder where you installed //Git Winch.// Read more about this [[org?do=export_xhtml|here.]] You MUST set a suitable organization/division code for yourself. This is a simple text written in a text file named //"orgname.txt"// which must be kept in the same folder where you installed //Git Winch.// Read more about this [[org?do=export_xhtml|here.]]
    
 +There is a special file named //gitwinch.ini// in the application folder. It is used to finely configure your own //Git Winch// as per your own office requirements. Use a text editor such as Notepad, Notepad++, VSCode, etc to edit it. How to set various configuration values in this ini file is explained [[inifile?do=export_xhtml|here]].
 +
 +There are several files after installation that you should definitely NOT delete or touch. However there are a few that can be configured specifically for your office. This is explained [[configuration?do=export_xhtml|here]] which you can read later if you are in a hurry now. 
 +
 +====Redistribution====
 +
 +Once you configure //Git Winch// specifically for your office, and the file "orgname.txt" is also written for your office; zip up the application folder and distribute that to your own office workers. The rest of your office then would have an easier time setting it up: They would mostly need to just extract the zip file into a new folder.
 +
 +And of course; everyone in the office, including you, should register. Explained next.
  
 ====Registration===== ====Registration=====
  
-To use //Git Winch// you not only need to install the software, but you should //also register.// Note that //Git Winch// can be privately hosted too. So you need to check where you have to register. If you got the zip file from our website; then the registration is done from a link given on our main website for //Git Winch// namely; https://gitwinch.com +To use //Git Winch// you not only need to install the software, but you should //also register.// And even the rest of your office who uses //Git Winch// should ALSO individually register.  
 + 
 +Note that //Git Winch// can be privately hosted too. So you need to check where you have to register. If you got the zip file from our website; then the registration is done from a link given on our main website for //Git Winch// namely; https://gitwinch.com 
  
 If you are running a privately hosted version of //Git Winch// you would need to ask the person who gave you the zip file (or you could look inside the //gitwinch.ini// file and read the value given for entry named: //"SystemAPIurl"// and go to the website mentioned there) If you are running a privately hosted version of //Git Winch// you would need to ask the person who gave you the zip file (or you could look inside the //gitwinch.ini// file and read the value given for entry named: //"SystemAPIurl"// and go to the website mentioned there)
Line 41: Line 56:
  
 None of the registrations expire. //(Of course, you can always exercise your right to be forgotten, and we'll delete all your data if you email us at admin@gitwinch.com)// None of the registrations expire. //(Of course, you can always exercise your right to be forgotten, and we'll delete all your data if you email us at admin@gitwinch.com)//
 +
 +====Lifetime purchase====
  
 In some seminars/webinars/private-demos we sell lifetime, private //Git Winch// instances. In such a case, your account would be loaded with 5 billion credits ... which is plenty for you and your people to use. Though the system will continue to have the capability to accept payments //(if you really want to give us a gift, for example :-))// but normally in such private installations, you need not make any payments as the credits would be sufficient.  In some seminars/webinars/private-demos we sell lifetime, private //Git Winch// instances. In such a case, your account would be loaded with 5 billion credits ... which is plenty for you and your people to use. Though the system will continue to have the capability to accept payments //(if you really want to give us a gift, for example :-))// but normally in such private installations, you need not make any payments as the credits would be sufficient. 
installation.1749780678.txt.gz · Last modified: by admin

Page Tools