From 770081397cf5f105697a94b0be65196863e31d6d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Thomas=20Gra=CC=88fenstein?= <mail@thomas-graefenstein.de>
Date: Sun, 22 Mar 2026 16:00:55 +0100
Subject: [PATCH] enhanced readme

---
 README.md | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/README.md b/README.md
index aa2c684..bb723f5 100644
--- a/README.md
+++ b/README.md
@@ -72,6 +72,44 @@ rsync -avz -e 'ssh -p 55' \
 
 The `.env` files are excluded because they contain secrets and should be created directly on the VPS from the `.env.example` templates.
 
+## Syncing via Git (recommended)
+
+Now that Gitea is running, you can clone the repo directly on the VPS instead of using rsync.
+
+### First-time setup on the VPS
+
+```bash
+# 1. Add your SSH key to Gitea (via https://git.t-gstone.de user settings)
+
+# 2. Clone the repo
+cd ~
+git clone ssh://git@git.t-gstone.de:2222/gstone/nextcloud-selfhosted.git
+cd nextcloud-selfhosted
+
+# 3. Create .env files from examples
+cp .env.example .env
+cp nextcloud/.env.example nextcloud/.env
+cp gitea/.env.example gitea/.env
+cp monitoring/.env.example monitoring/.env
+
+# 4. Edit each .env file with real values
+nano .env
+nano nextcloud/.env
+nano gitea/.env
+nano monitoring/.env
+
+# 5. Deploy
+sudo ./scripts/deploy.sh
+```
+
+### Updating the VPS after pushing changes
+
+```bash
+cd ~/nextcloud-selfhosted
+git pull
+sudo docker compose --env-file .env up -d
+```
+
 ## Quick Start
 
 ```bash