Runtime & Deployment

Logidav has web, command and queue entry points. The deployed topology, PHP version, active scheduler, worker manager and deployment process have not been verified for a specific environment. Confirm these with the system owner before using them for an incident or release.

Jobs and queues

• The historical crontab is a dated snapshot, not evidence of the current schedule or host.
• The queue model describes the reviewed source paths. A queue record does not by itself prove that a worker is running or that a destination accepted the work.
• Some commands implement locks. Consult the relevant workflow for its exact lock and failure boundaries; do not assume every command releases a lock or retries in the same way.

Start with order import for cursor and status jobs, and cron incident triage when investigating a failure.

Deployment and configuration

The current deployment pipeline, schema-change process, cache procedure and runtime settings require environment-specific verification. In particular, do not apply a generic schema update, restart a worker or run a job as a diagnostic shortcut. Production diagnostics require approval for the exact command and target; deployment and recovery actions require separate authorization.

See configuration for the source-template boundary and deployment reference for the existing deployment notes, which also need verification before operational use. The documentation site uses VitePress; a successful local build is separate from deployed-site access.