Overview

Admin panel is located in General configuration → Administration → Git4C Admin.

1. List of Predefined repositories
2. Button for adding predefined repository
3. Indicator if files from this repository can be edited
4. Button for editing a given predefined repository
5. Remove given predefined repository button
6. List of predefined filters
7. Button for adding a predefined filter
8. Remove given predefined filter button
9. List of macros in system
10. Button to show/hide list of macros
11. Macro type indicator
12. Macro healthcheck
13. Remove all filters and restore default ones
14. Clean all unused data
15. Remove all plugin data
16. Force users to use predefined repositories only
17. Thread settings

Cleaning data

To remove all plugin click “Clean data” on the bottom of the page. To confirm action click “Clean”.

Creating predefined repository

You can create new predefined repository by clicking “Add Predefined Repository”.

After clicking the button a dialog would show up.

You can change authorization type to SSH or HTTP username and password.

Removing predefined repository

You can remove predefined repository by clicking bin icon on the right-hand site. To confirm deletion click “Remove” button in dialog that would show up.

Creating new filter

You can create new predefined repository by clicking “Add predefined filter”.

Git4C uses Glob for filtering files. https://docs.oracle.com/javase/tutorial/essential/io/fileOps.html#glob

Removing filter

You can remove filter by clicking bin icon on the right-hand site. To confirm deletion click “Remove” button in dialog that would show up.

Restoring filter

To restore default filters click “Restore default filters” at the bottom of the page. To confirm click “Restore” button in dialog that would show up.

Forcing predefined repositories

Git4C offers a possibility to allow users creating macro only with predefined repositories.

To block custom repositories simply switch the toggle button on.

Remember, this will only block creating a new macro with custom repository. Those already craeted will still be functional and editable.

To confirm this action click the Block button on warning dialog.

Changing number of used threads

In version 1.4.0 we’ve changed backend architecture to asynchronous one. Due to these changes we’re allowing administrators to set number of used thread to utilize workload specifically for server specification.

1. Number of threads used for revision checking
2. Number of threads used for repository pulling
3. Number of threads used for converting documents
4. Number of threads used for heavy I/O operations (like indexing macros using DB)
5. Button to save settings