Storage Under the Hood A Custom Credential Cache Summary Customizing Git Git Configuration Basic Client Configuration Colors in Git External Merge and Diff Tools Formatting and Whitespace Server Configuration Hooks Installing a Hook Client-Side Hooks Server-Side Hooks An Example Git-Enforced Policy Server-Side Hook Client-Side Hooks Summary Git and Other Systems Git as a Client Git and Subversion Git what, and it’s far easier to administer a CVCS than it is to deal with local databases on every client. However, this setup also has some serious downsides. The most obvious is the single point of failure

Storage Under the Hood A Custom Credential Cache Summary Customizing Git Git Configuration Basic Client Configuration Colors in Git External Merge and Diff Tools Formatting and Whitespace Server Configuration Hooks Installing a Hook Client-Side Hooks Server-Side Hooks An Example Git-Enforced Policy Server-Side Hook Client-Side Hooks Summary Git and Other Systems Git as a Client Git and Subversion Git what, and it’s far easier to administer a CVCS than it is to deal with local databases on every client. However, this setup also has some serious downsides. The most obvious is the single point of failure

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Git as a Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . what, and it’s far easier to administer a CVCS than it is to deal with local databases on every client. However, this setup also has some serious downsides. The most obvious is the single point of failure history. Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it. Every clone is really a full backup

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 10 Weblate Client 251 10.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 10 Weblate Client 251 10.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 10 Weblate Client 253 10.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 10 Weblate Client 239 ii 10.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 10 Weblate Client 237 ii 10.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 10 Weblate Client 239 ii 10.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there

GitHub Mercurial Subversion Weblate’s Web API REST API Notification hooks Exports RSS feeds Weblate Client Installation Synopsis Description Files Examples Weblate’s Python API Instalation wlc wlc.config achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to your repository and configure Push URL achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your repository to trigger Weblate whenever there