OPERATIONS

Know what changed. Know what is running.

Bring application ownership, release history, resource policy, and domain state into a single operational workflow.

One operational record for every website

The panel connects a website to its workspace, environment, release, runtime, and domains. Operators can distinguish a requested change from a runtime observation before deciding what to do next.

01 Identify the change02 Inspect the evidence03 Decide the recovery
RUNBOOK 01

A release does not become ready

The new runtime fails readiness or has no current observation.

Investigation

  1. Confirm the intended artifact, PHP engine, and document root.
  2. Check startup errors, required extensions, mount permissions, and secret resolution.
  3. Keep the existing release serving until the replacement is verified.

DecisionRecord the failure and prepare a corrected release. Missing evidence must remain visible.

RUNBOOK 02

An application reaches its capacity limit

Errors, latency, or resource observations indicate pressure.

Investigation

  1. Compare CPU, memory, process, and storage use with the assigned policy.
  2. Inspect queue backlog, external service latency, and application logs.
  3. Measure a staging change before increasing capacity or changing worker settings.

DecisionDistinguish a capacity problem from a slow query, a provider failure, or an application defect.

RUNBOOK 03

A domain is not serving securely

Ownership, DNS routing, or TLS does not match the intended configuration.

Investigation

  1. Verify the domain owner and the current authoritative nameservers.
  2. Inspect the application target and DNS records without assuming propagation.
  3. Check certificate issuance and renewal state independently of deployment health.

DecisionRestore the correct route only after ownership and TLS checks pass.

RUNBOOK 04

Restore the previous application release

A verified release introduces a regression after traffic has switched.

Investigation

  1. Identify the last suitable artifact and its runtime configuration.
  2. Confirm database schema and persistent data remain compatible.
  3. Record the approval, execute the recovery procedure, and check the resulting endpoint.

DecisionA successful application rollback needs fresh runtime evidence and a separate data recovery decision.

What an operator needs to see
RecordWhat it answers
Website and environmentWho owns this application and where should it run?
Release and artifact digestWhich code and runtime configuration are being deployed?
Health and observationHas the node actually reported the expected result?
Audit and rollback referenceWho changed it, and which known release can be restored?
YOUR APPLICATION. YOUR WORKFLOW.

Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.