Operations
Because Nona is self-hosted, operating the service is part of the product story.
This section covers the core operational topics that sit next to deployment:
- security and authentication
- single sign-on
- backups
- upgrades
In this section
Section titled “In this section”Typical operator tasks
Section titled “Typical operator tasks”Once Nona is live, the usual operational work is:
- secure admin access
- manage users and project access
- back up
/var/lib/nona - review audit history after sensitive changes
- upgrade the container without losing persistent data
That is the sequence this section is designed to support.
When to read this section
Section titled “When to read this section”Use these docs when:
- you are preparing a production deployment
- multiple teams or users will operate the service
- you are planning maintenance work
- you want a safer self-hosted operating model
Start here
Section titled “Start here”If you are setting up a real production instance, begin with:
Related docs
Section titled “Related docs”When should I start reading the operations docs?
Section titled “When should I start reading the operations docs?”Start when you are preparing a real production deployment or when more than one person will operate the instance.
Are operations docs only about infrastructure?
Section titled “Are operations docs only about infrastructure?”No.
They also cover operator workflows such as admin access, backups, upgrades, and reviewing operational history.
What should I secure first in a production setup?
Section titled “What should I secure first in a production setup?”Start with admin access and authentication, then make sure backups are in place before treating the instance as production-ready.
Why are operations part of the product story for Nona?
Section titled “Why are operations part of the product story for Nona?”Because Nona is self-hosted.
That means operating the service is part of using the product correctly, not a separate concern you can ignore.