Avii/Radicale
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Update DOCUMENTATION.md

Browse Source 
Explain possible pitfall when using git with systemd
This commit is contained in:
G-Huber
2023-10-31 23:13:46 +01:00
committed by GitHub
parent d7ce2f0b98
commit 02c949d5d3
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
DOCUMENTATION.md
View File

@@ -528,6 +528,16 @@ git add -A && (git diff --cached --quiet || git commit -m "Changes by "%(user)s)
The command gets executed after every change to the storage and commits The command gets executed after every change to the storage and commits
the changes into the **git** repository. the changes into the **git** repository.
For the hook to not cause errors either **git** user details need to be set and match the owner of the collections directory or the repository needs to be marked as safe.
When using the systemd unit file from the [Running as a service](#running-as-a-service) section this **cannot** be done via a `.gitconfig` file in the users home directory, as Radicale won't have read permissions!
In `/var/lib/radicale/collections` run:
```bash
git config user.name "radicale"
git config user.email "radicale@example.com"
```
## Documentation ## Documentation
### Configuration ### Configuration