pez-docs/workloads/nextcloud/README.md
Pez 8e7269611d Update docs to reflect current setup (March 2026)
- Add Hetzner Cloud location (helsinki-a, nuremberg-a)
- Update london-a to FreeBSD, london-b ZFS layout to 3x raidz1
- Note offline servers (london-c, copenhagen-b)
- Update Plex docs with accurate ZFS and exporter behaviour
- Add workload docs: Nextcloud AIO, Navidrome, slskd, Monitoring,
  Auth (Authelia/LLDAP/Bitwarden), Mail (poste.io), Gaming (Minecraft/MaNGOS)
- Update README/intro with current service and location index
2026-03-04 09:09:08 +00:00

28 lines
963 B
Markdown

# Nextcloud
## Why
Nextcloud is my self-hosted alternative to Google Drive / iCloud. It handles file sync across devices, calendar, contacts, and a few other things.
## Setup
Running **Nextcloud AIO** (All-In-One) on `london-b` via Docker. AIO bundles Nextcloud itself with all the supporting services into a managed stack:
- Nextcloud (PHP-FPM)
- PostgreSQL
- Redis
- Elasticsearch (full-text search)
- Collabora Office (online document editing)
- Imaginary (image processing)
- Notify Push (real-time push notifications)
- Whiteboard
The AIO master container manages updates and health for all of these, which keeps maintenance overhead low.
## Storage
Files live on `london-b`'s ZFS pool (`hdd`), giving plenty of room to grow. ZFS gives checksumming and integrity verification essentially for free, which is nice to have under a file sync service.
## Access
Exposed via Caddy on `helsinki-a` through a Cloudflare tunnel, with Authelia SSO in front.