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:28] admininstallation [2025/06/13 04:31] (current) admin
Line 12: Line 12:
  
 **//Chrome (or a browser similar to Chrome) is needed!//**\\ **//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.+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. 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.
Line 33: 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 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]].  
- 
- 
 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 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==== ====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. 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)
installation.1749781683.txt.gz · Last modified: by admin