Administration guide
Browse by topic
Explore related documentation through its most useful keyword groups.
31 items
Grouped by Domain
Defining site module runtime and service settings.
Creating configuring updating starting and stopping Zotonic sites.
Determining which users may view change or administer resources and operations.
Recording and observing events errors state health and performance.
Preserving and recovering site data media and configuration.
Managing files and media resources throughout their lifecycle.
Managing users login identities account data and account lifecycle.
Sending queuing relaying and tracking outgoing email.
Persisting media previews archives and other managed files locally or remotely.
Explore this clusterDocumentation not covered by the other keyword groups in this split.
Explore this clusterPrepare translations before making a language visible to visitors.
Give an account the permissions required for its work.
Choose the right configuration layer and verify the effective value.
Verify host, role, database, and schema before restarting a site.
Monitor the user-facing service as well as its processes.
Use the right management surface and account.
Keep original uploads accessible across deployments and restarts.
Align DNS, site selection, and certificate termination.
Check media-process isolation and decide whether to run conversions on a separate service.
Set a relay at the correct scope and test a real site message.
Run Zotonic under the installation’s service manager.
Request a backup and verify its completion and scope.
Choose recovery coverage, retention, and an owner.
Apply a tested revision and check the site from a visitor’s perspective.
Separate node, site, database, and application failures.
Locate the failure in permission, storage, or processing.
Trace one message from request to recipient.
Prevent an acceptance workflow from emailing real users.
Change module activation and verify the affected workflow.
Give the next operator enough context to continue safely.
Test version-specific changes and establish a recovery point.
Separate environments and record how the site is operated.
Recover code and data to a compatible state.
Find the relevant failure without exposing credentials or personal data.
Use revisions or deleted-page recovery for an editorial mistake.
Restore into isolation and verify content, media, and access.
Remove login methods and permissions without deleting their authored content.
Find obsolete access and verify who can administer the site.
Coordinate changes and verify service before reopening access.
Adjust group upload limits and test with an ordinary account.
Check a rule change before it affects everyone.