Self-hosting¶
NetRoll ships as one container image — a single binary serving the built SPA — plus a Postgres database. Nothing in it requires infrastructure operated by N1CCK: no tailnet, no 1Password, no particular host.
Get started¶
- Self-hosting quickstart — a working instance from a compose file in about ten minutes.
Guides¶
- Use the admin dashboard — review abuse reports, disable an account, and read the audit log.
- Enable analytics — optional, cookie-less, self-hosted Plausible. Off unless you turn it on.
- Upgrade an instance — pin a version, upgrade, and roll back.
Learn more¶
- Deployment model — what's in the image, what state exists, and what the app does at boot.
Reference¶
- Configuration — every environment variable, its default, and whether an invalid value is a hard boot error.
- Troubleshooting self-hosting — boot failures, mail problems, and lost avatars.
What you're responsible for¶
| Concern | Handled by NetRoll | Handled by you |
|---|---|---|
| Schema migrations | Yes — applied at boot | — |
| TLS and the public hostname | No | Your reverse proxy |
| Outgoing email | Sends via SMTP | Supplying a working relay and a sender domain |
| Backups | No | Postgres dumps and the avatar volume |
| Exposure control | No | Your firewall and proxy |