LaraDep Documentation
You are reading Managed mode
Managed onboarding and preflight checklist
Detailed checklist for preparing, starting, and validating the first operational run in managed mode. Goal: prevent avoidable errors before production deployment.
Managed onboarding and preflight checklist
Managed mode is designed for predictable operations. This page standardizes what to complete before the first run so your team does not start with avoidable uncertainty.
Purpose and target audience
- Fast start without owning deployment infrastructure,
- clear pre-run validation before critical operations,
- shared operating rhythm across operators.
Prerequisites
- The workspace is created in the correct tenant context,
- server is attached and SSH access is defined via approved credentials,
- selected template matches the target use case (Laravel Smart/Lite, WordPress, Docker, etc.),
- at least one operator understands roles and approval flow.
Step-by-step process
- Define scope and target outcome — what should onboarding deliver, which service should be reachable, and who owns review.
- Run onboarding flow in managed onboarding and complete all required inputs.
- Validate first-run values — domain, passwords, DB values, mail/SSL choices, and optional webhook values.
- Run preflight and resolve all warning/error states before execution.
- Execute the first run with a minimal safe tag set for baseline validation (for example
init,web,tls,db,deploy). - Validate deployment result by checking target service, TLS status, and run history.
- Close the run with notes: who triggered, who verified, and pending follow-up tasks.
Pre-production checklist
- Is server connectivity and target workspace mapping valid in preflight?
- Are all required onboarding values valid and explicitly reviewed?
- Is an approver and rollback path defined?
- Has the deployment window been confirmed?
- Does run history include enough context for audit review?
Common mistakes
- Running outside approved maintenance window,
- ignoring preflight warnings because they are “non-blocking”,
- missing single approver ownership,
- unclear operational ownership after the run.
Next steps
- For recurring run standards go to managed operations and governance.
- For deeper control over playbook and tag behavior, read the deployment and preflight guide.
- Use workspaces and access controls for team separation.
- For mode decisions, compare managed vs self-hosted and review mode migration flow.
Next step: Move to managed governance checklist for role ownership, audit evidence, and change windows.