Differences

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

--- advanced [2025/05/12 09:06] – created admin
+++ advanced [2025/06/02 18:48] (current) – admin
@@ Line 1: / Line 1: @@
 ======Advanced usage of Git Winch======
-//Git Winch// has been designed so that people who are not very familiar with //Git// can also use it. The reason for using //Git// is because the Git ecology is very robust for both keeping backups //as well as// for version control.
+//Git Winch// has been designed so that people who are not very familiar with //Git// can also use it. The reason for using //Git// is because the Git ecology is very robust for both keeping backups //as well as// for version control. However //Git Winch// can be put to more advanced uses too -- useful for those who want to achieve more from this utility.
-As //Git Winch// works with all the popular Git hosts such as Gitlab, Github and Gitea, it would serve our users admirably well. In fact, you can have your own self-hosted version of Gitlab or Gitea, and with just some minor changes in the gitwinch.ini file and the config.txt file, you can easily run a completely private version of //Git Winch//
 **Configuring for self-hosted Gitea or Gitlab**\\
-//will document this soon//
+As //Git Winch// works with all the popular Git hosts such as Gitlab, Github and Gitea, it would serve our users admirably well. In fact, you can have your own self-hosted version of Gitlab or Gitea, and with just some minor changes in the gitwinch.ini file and the config.txt file, you can easily run a completely private version of //Git Winch//
-**Using //Syncthing//**\\
-Syncthing (https://syncthing.net) is also a very powerful peer-to-peer backup and synchronization system. The advantage of using Syncthing is that you do not need an external hosting service -- the way you do with Git.  However, there are some notable disadvantages (listed below) and hence we recommend Syncthing to be used only in case of a few known individuals working together in an office. We do NOT recommend that you use Syncthing for everyone in the office.
-This is how you can setup Syncthing to work with //Git Winch//\\
-//will document this soon//
-**Disadvantages of Syncthing**\\
+**Other advanced uses**\\
-  * There is no //commit, push, pull, etc// when you work on a folder managed by Syncthing. Whatever that is done on such a folder will get 'synced' to the same folder that is present in other users' respective folder. That means if someon decides to delete a file, then practically immediately the same file would get deleted in others' folders too. (You can mitigate this issue by asking //Syncthing// to preserve versions)
+  * [[advancednotes?do=export_xhtml |Using TortoiseGit and Git command line]]
-  * It currently does not have an easy way to detect if a //sync// has got complete in an automatic manner. So one cannot automatically call a build process  -- something that is easily possible after a //git push//
+  * [[syncthing?do=export_xhtml |Using Syncthing]]
+  * [[hashtagcapture?do=export_xhtml|Clipboard Capture]]
+  * [[build?do=export_xhtml|Build Automation]]
+  * [[ignoredfiles?do=export_xhtml|Ignoring temporary files]]
+-----
+[[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]]

Git Winch Guide

Differences

Page Tools