# Nextcloud Decisions

## 2026-05-12 — Use Nextcloud as operational platform

Decision: Nextcloud is intended to support collaboration, tasks, calendar, communication, and later file storage.

Reason: The user wants a shared platform to reduce overwhelm and support Pi-assisted personal operations.

## 2026-05-12 — Prefer dedicated VM

Decision: Prefer deploying Nextcloud on a dedicated VM.

Reason: Major services are easier to back up, snapshot, isolate, and reason about when separated from unrelated workloads.

## 2026-05-13 — Initial Nextcloud access model

Decision: Initial Nextcloud access should be LAN and Tailscale, using `nc.dropcutstud.io` as the intended hostname.

Reason: This supports remote/private access without immediately exposing the service publicly.

## 2026-05-13 — Recommended deployment method

Decision: Recommend Docker Compose on a Debian/Ubuntu VM with Nextcloud, PostgreSQL, and Redis.

Reason: This is maintainable for a single-person homelab, transparent for learning, flexible with reverse proxies/DNS, and less opinionated than AIO or Snap.

## 2026-05-13 — Initial storage target

Decision: Allocate about 80 GB initially.

Reason: This is enough for initial collaboration/tasks/calendar usage while postponing larger storage planning.

## 2026-05-13 — Backup gap acknowledged

Decision: Do not treat the deployment as production/important-data-ready until a backup destination and restore approach exist.

Reason: There is currently no backup destination.