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
concepts [2025/06/12 05:56] – adminconcepts [2025/06/17 16:55] (current) – admin
Line 5: Line 5:
 Think of it as a simple replacement for the usual //Windows File Explorer.// You would start the //Git Winch Client Application// when you start the day at the office. And that is the last application you would close, when you are about to exit the office for the day. Think of it as a simple replacement for the usual //Windows File Explorer.// You would start the //Git Winch Client Application// when you start the day at the office. And that is the last application you would close, when you are about to exit the office for the day.
  
-Firstly, understand the who/what/how/why of this simple, elegant, way of working at an office. Then you should have a broad overview on its inner workings.+(If you have time, read the [[background?do=export_xhtml|Philosophy and Background]] before the rest of this document. It is //optional.// But do read it sometime.) 
 + 
 +Firstly, understand the who/what/how/why of this simple, elegant, way of working at an office. Then you should have a broad overview on its inner workings.  
      
  
Line 67: Line 70:
 We thought long and hard about this, and since //Git Winch// can be used in any kinds of offices we found that this best for all situations. For example; startup comprising of 4 partners can use //Git Winch// and each one pay for their own usage. But in another case, if an office employs a temporary worker, the owner can transfer some of his/her credits to that worker as needed. We thought long and hard about this, and since //Git Winch// can be used in any kinds of offices we found that this best for all situations. For example; startup comprising of 4 partners can use //Git Winch// and each one pay for their own usage. But in another case, if an office employs a temporary worker, the owner can transfer some of his/her credits to that worker as needed.
  
-//**NOTE:**// In some events (e.g. when we conduct special demos) we also offer full lifetime purchase too and multiple ways to set this up -- for example; you can setup the coordination server at your own dedicated or VPS server too. The lifetime-price would be announced at those events. +//**NOTE: In some events (e.g. when we conduct special demos) we also offer full lifetime purchase too and multiple ways to set this up -- for example; you can setup the coordination server at your own dedicated or VPS server too. The lifetime-price would be announced at those events.**// 
  
 =====User Interface===== =====User Interface=====
Line 78: Line 81:
  
 **Some points you may need to know:**\\  **Some points you may need to know:**\\ 
-The application does not have a //close// or //quit// button. You can simple use the 'x' at the top right of the windows inside //Git Winch.// +The application does not have a //close// or //quit// button. You can simply use the 'x' at the top right of the windows inside //Git Winch.// 
  
 For help, even if you hover over a component and press //F1// hot-key, it will display a context-sensitive help. In fact this is a good way to learn //Git Winch//. Just hover over any of the UI elements and when you see a small status-bar help for that, press F1 to learn more about that. For help, even if you hover over a component and press //F1// hot-key, it will display a context-sensitive help. In fact this is a good way to learn //Git Winch//. Just hover over any of the UI elements and when you see a small status-bar help for that, press F1 to learn more about that.
Line 89: Line 92:
 What is wrong with that, you can ask? Sometimes this can be okay. But there can be subtle issues. And when the issues do turn up, they an be a serious headache; often unsolvable if you did not use //Git Winch//. What is wrong with that, you can ask? Sometimes this can be okay. But there can be subtle issues. And when the issues do turn up, they an be a serious headache; often unsolvable if you did not use //Git Winch//.
  
-For example; if you edit and save the file and then quit Word, and later on you again load it into Word at some other time and you say "Ah, I really want the older version. I think that was better" -- now you are stuck. Because Microsoft word has already overwritten it!+For example; if you edit and save the file and then quit Word, and later on you again load it into Word at some other time and you say "Ah, I really want the older version. I think that was better" -- now you are stuck. Because Microsoft word has already overwritten it! 
  
-Using //Git Winch//, you are requested to do two additional steps. Before you launch the word file, you would request //Git Winch// to do a //git pull// That action will result in fetching the very latest version from the central repository... That means, if someone else had been working on the same file before you, now you would get the one that he had worked upon!+That's why //Git Winch// has an elegant way to revert back to earlier versions of such a file. 
 + 
 +Using //Git Winch// on a day-to-day basis, you are requested to do two additional steps. Before you launch the word file, you would request //Git Winch// to do a //git pull// That action will result in fetching the very latest version from the central repository... That means, if someone else had been working on the same file before you, now you would get the one that he had worked upon!
  
 And the second action is done //after// you had edited and saved the edited file. This time, you need to //push // the file back to the central repository. The usual action you need to invoke, is called //add and send//  And the second action is done //after// you had edited and saved the edited file. This time, you need to //push // the file back to the central repository. The usual action you need to invoke, is called //add and send// 
Line 98: Line 103:
  
 Since you //bracketed// the normal work you do between a //pull// and a //push// action, //Git Winch// ensures that your work is made available to others too -- so you can work from home, do all the above (bracketed between "pull" and "push") and somewhere else, your colleague can also do the same sequence of activities, and thereby both of you end up working collaboratively. Since you //bracketed// the normal work you do between a //pull// and a //push// action, //Git Winch// ensures that your work is made available to others too -- so you can work from home, do all the above (bracketed between "pull" and "push") and somewhere else, your colleague can also do the same sequence of activities, and thereby both of you end up working collaboratively.
 +
 +Each "Push" results in a new "Commit ID" at the Git System. You can easily read the history of the commits and revert the file (or the entire repository) to any of those Commit IDs.
  
 **IMPORTANT**\\ **IMPORTANT**\\
 Of course, the owner/manager would need to first have the files stored in the central repository at one of the compatible Git hosting service (either //Gitlab// or //Github// or //Gitea//) and that person should get the correct API key too for that host. See [[/tsmanage2?do=export_xhtml|management]].  Of course, the owner/manager would need to first have the files stored in the central repository at one of the compatible Git hosting service (either //Gitlab// or //Github// or //Gitea//) and that person should get the correct API key too for that host. See [[/tsmanage2?do=export_xhtml|management]]. 
  
-A very useful advantage of //Git Winch// is that everyone works using //SSH Deploy keys//. This is highly secure. As the Deploy Key can easily be deleted by the repository owner in a second, the moment an office worker quits (or is terminated) in an office, that person's Deploy Key is deleted and the person no longer has access to any data that he/she had access to earlier. +A very useful advantage of //Git Winch// is that everyone works using //SSH Deploy keys//. This is highly secure. The moment an office worker quits (or is terminated) in an office, that person's Deploy Key can be deleted in a second and the person no longer has access to any data that he/she had access to earlier. 
  
-Only the repository owner need to have an account at one of the aforesaid Git hosts. The rest of the people who are 'members' that work on that repository do NOT need a membership at that Git host. +Only the repository owner need to have an account at one of the aforesaid Git hosts. The rest of the people who are 'members' that work on that repository do NOT need a membership at that Git host. Everyone; including the owner, does the Git work using the aforementioned Deploy Keys.
  
 **Groups**\\ **Groups**\\
concepts.1749700587.txt.gz · Last modified: by admin

Page Tools