This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| advantages [2025/06/29 10:59] – admin | advantages [2025/07/09 11:16] (current) – admin | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * //Git Winch// is totally file-agnostic. What this means is that the office is free to use //any// file they choose. We do NOT lock you into any files. We do not put you into our " | * //Git Winch// is totally file-agnostic. What this means is that the office is free to use //any// file they choose. We do NOT lock you into any files. We do not put you into our " | ||
| + | | ||
| + | * You can create template files for //ALL// the files your office uses. This ensures that you can create a new file for //any// application you use, right from within //Git Winch.// For e.g. you can immediately work on a new letter with your office letterhead on it. | ||
| * We do NOT make offices transmit files //through our server.// This is a huge deal, if you think deeply. In today' | * We do NOT make offices transmit files //through our server.// This is a huge deal, if you think deeply. In today' | ||
| | | ||
| - | * There are many office systems that allows you to //attach// files and then send those files to others. For e.g. Slack or Microsoft Teams. This is actually a serious headache, which needs a deeper explanation. Read about the [[vfour? | + | * There are many office systems that allows you to //attach// files and then send those files to others. For e.g. Slack or Microsoft Teams. This is actually a serious headache, which needs a deeper explanation. Read about the [[vfour? |
| * //Git Winch// will keep other members working on the files in a repository informed about which files they are working. It prevents the same file being worked-upon, | * //Git Winch// will keep other members working on the files in a repository informed about which files they are working. It prevents the same file being worked-upon, | ||
| Line 15: | Line 17: | ||
| * Members can leave additional notes on each and every file, if they so want – such meta-information about files can be very useful to help others working on those files. | * Members can leave additional notes on each and every file, if they so want – such meta-information about files can be very useful to help others working on those files. | ||
| - | * The coordination server of //Git Winch// only stores the file-paths and that too only for those files your office is working on. Not the data itself. This is for coordinating the work and reducing chances of clashes. | + | * The coordination server of //Git Winch// only stores the file-paths and that too only for those files your office is working on. Not the data itself. This is for coordinating the work and reducing chances of clashes. In short, we never intrude into your privacy. |
| * The owner/ | * The owner/ | ||
| Line 21: | Line 23: | ||
| * Your files are not only backed up at the Git Host of your choice, but you and your office can //revert// back to previous version of the same files. This is especially a major advantage for creative offices such as graphic artists, marketing agencies, architects... | * Your files are not only backed up at the Git Host of your choice, but you and your office can //revert// back to previous version of the same files. This is especially a major advantage for creative offices such as graphic artists, marketing agencies, architects... | ||
| - | * The office workers need not have any account at the Git Host. Only the owner takes such an account. In fact even the owner just sets up a special Personal Access Token, on the host and nothing much else there. The advantage of using //Git Winch// to manage Github/ | + | * The office workers need not have any account at the Git Host. Only the owner takes such an account. In fact even the owner just sets up a special Personal Access Token (PAT), on the chosen Git host and nothing much else there. The advantage of using //Git Winch// to manage Github/ |
| + | |||
| + | * If the owner is too busy, all he/she has to do is to delegate the rest of the setting up work to a manager. The owner does NOT share the PAT but instead an encrypted version can be shared with the said manager to do the work on behalf of the owner. This ensures that the PAT never goes astray and yet, work can be delegated to the said manager. You can have any number of managers | ||
| * The system allows owners/ | * The system allows owners/ | ||
| Line 39: | Line 43: | ||
| * If by some chance you need to do some advanced Git commands, you can easily drop into a console window, and carry out the actions using command-line Git. You can also use the popular // | * If by some chance you need to do some advanced Git commands, you can easily drop into a console window, and carry out the actions using command-line Git. You can also use the popular // | ||
| - | * ALL commits pushed into your Git host are //signed.// That means there is NO chance that anyone can forge someone else's name into a commit and then push it. All signatures are verifiable by anyone who has access to that repositories. Even if the original author is no longer part of the office, that person' | + | * ALL commits pushed into your Git host are //signed.// That means there is NO chance that anyone can forge someone else's name into a commit and then push it. All signatures are verifiable by anyone who has access to that repository. Even if the original author is no longer part of the office, that person' |
| - | < | + | *< |
| ----- | ----- | ||
| [[/ | [[/ | ||