Self-Host Nextcloud with Greffon: Own Your Files
Files, calendar, contacts, and shared documents, on a server you own instead of a subscription you rent. Here is the honest setup for Nextcloud on a greffer.
Nextcloud is the closest thing the self-hosting world has to a full Dropbox-plus-Google-Workspace replacement: file sync, sharing, calendar, contacts, and document collaboration. It is also a big platform, and being honest about that up front is the difference between a setup you keep and one you abandon. Grafting it onto a greffer puts all of it on your hardware.
Why own your files
The pitch is simple: your files, calendar, and contacts sync across every device, and they live on a machine you control rather than a provider you pay monthly. Nextcloud has a mature desktop client and mobile apps, so in daily use it feels like the commercial options. The data underneath is yours.
Graft it from the catalog
Pick Nextcloud from the catalog and graft it onto your greffer. Greffon handles the certificate and the reverse proxy, including the trusted-domain wiring Nextcloud needs to serve over HTTPS, so you are not editing config files to get past the first screen.
Reach it from your devices
Sync is only useful if every device can reach the server. On your own network it works immediately. From outside, tunnel mode lets the greffer serve Nextcloud with no inbound ports, the simplest path behind NAT, or you can port-forward and use dynamic DNS. The desktop and mobile clients then sync over HTTPS from anywhere.
The hardware it rewards
Nextcloud will technically start on very little, but it rewards a real box. Files need disk that grows with your library, and the app server and database are happier with a couple of real CPU cores and a sensible chunk of memory, especially once a few people or several devices are syncing at once. A small always-on machine is fine for a personal setup; a household or team should plan for more.
Back it up first
Once Nextcloud is where your files live, its backup is your backup. Greffon handles TLS and routing today; native one-click backups land in M2. Until then, bring your own tool (restic or borgbackup), back up the data directory and the database together on a schedule, and keep a copy off the greffer.
