113 lines
2 KiB
Markdown
113 lines
2 KiB
Markdown
|
# Administrator-Handbuch – [PROJEKT_NAME]
|
|||
|
|
|
|||
|
|
> Zielgruppe: **Administratoren** – Menschen, die das System betreiben, deployen und konfigurieren.
|
|||
|
|
> Voraussetzung: Grundkenntnisse in Linux, Docker und dem eingesetzten Stack.
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Systemvoraussetzungen
|
|||
|
|
|
|||
|
|
<!-- TODO: Anforderungen an Host/Server -->
|
|||
|
|
|
|||
|
|
| Komponente | Mindestanforderung | Empfohlen |
|
|||
|
|
|---|---|---|
|
|||
|
|
| OS | … | … |
|
|||
|
|
| RAM | … | … |
|
|||
|
|
| Disk | … | … |
|
|||
|
|
| Dependencies | … | … |
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Deployment
|
|||
|
|
|
|||
|
|
### Erstes Aufsetzen
|
|||
|
|
|
|||
|
|
<!-- TODO: Schritt-für-Schritt Deployment -->
|
|||
|
|
|
|||
|
|
```bash
|
|||
|
|
# Beispiel
|
|||
|
|
git clone <repo> /opt/service
|
|||
|
|
cd /opt/service
|
|||
|
|
cp .env.example .env
|
|||
|
|
# .env ausfüllen!
|
|||
|
|
docker compose up -d
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
### Updates einspielen
|
|||
|
|
|
|||
|
|
<!-- TODO: Update-Prozedur -->
|
|||
|
|
|
|||
|
|
```bash
|
|||
|
|
git pull
|
|||
|
|
docker compose pull
|
|||
|
|
docker compose up -d --force-recreate
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Konfiguration
|
|||
|
|
|
|||
|
|
### Umgebungsvariablen (`.env`)
|
|||
|
|
|
|||
|
|
<!-- TODO: Alle relevanten Env-Vars dokumentieren -->
|
|||
|
|
|
|||
|
|
| Variable | Pflicht | Default | Beschreibung |
|
|||
|
|
|---|---|---|---|
|
|||
|
|
| `EXAMPLE_VAR` | ✓ | – | Beschreibung |
|
|||
|
|
|
|||
|
|
### Persistente Daten (`/data/`)
|
|||
|
|
|
|||
|
|
Alle persistenten Daten liegen unter `/data/<service>/` im Repo-Root:
|
|||
|
|
|
|||
|
|
<!-- TODO: Alle Service-Unterordner und was drin liegt -->
|
|||
|
|
|
|||
|
|
| Pfad | Inhalt | Backup-Priorität |
|
|||
|
|
|---|---|---|
|
|||
|
|
| `data/<service>/` | … | hoch/mittel/niedrig |
|
|||
|
|
|
|||
|
|
**Backup-Hinweise:**
|
|||
|
|
- `/data/` komplett sichern vor jedem Update
|
|||
|
|
- Empfehlung: tägliches Backup via Cron / Restic / rsync
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Monitoring & Logs
|
|||
|
|
|
|||
|
|
<!-- TODO: Wie überwacht man das System? Wo sind die Logs? -->
|
|||
|
|
|
|||
|
|
```bash
|
|||
|
|
# Logs ansehen
|
|||
|
|
docker compose logs -f <service>
|
|||
|
|
|
|||
|
|
# Status prüfen
|
|||
|
|
docker compose ps
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Sicherheit
|
|||
|
|
|
|||
|
|
<!-- TODO: Firewall-Regeln, Portfreigaben, TLS-Setup etc. -->
|
|||
|
|
|
|||
|
|
- Offene Ports: …
|
|||
|
|
- TLS: …
|
|||
|
|
- Zugriffskontrolle: …
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Troubleshooting
|
|||
|
|
|
|||
|
|
| Symptom | Ursache | Lösung |
|
|||
|
|
|---|---|---|
|
|||
|
|
| … | … | … |
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## Disaster Recovery
|
|||
|
|
|
|||
|
|
<!-- TODO: Was tun wenn es brennt? -->
|
|||
|
|
|
|||
|
|
1. Dienst stoppen: `docker compose down`
|
|||
|
|
2. Backup einspielen: …
|
|||
|
|
3. Dienst neu starten: `docker compose up -d`
|