LaraDep Documentation
You are reading Self-hosted mode
Self-hosted templates and workflow
How to set templates and workflow in self-hosted mode for stable deployments, predictable auditability, and less operator improvisation.
Self-hosted templates and workflow
Self-hosted mode gives flexibility, but without shared templates it quickly drifts into ad-hoc operations. This page defines how to maintain a repeatable deployment pattern.
Purpose
- Reduce improvisation,
- increase run repeatability,
- link templates to governance and workspace ownership.
Practical model
- Define common playbook patterns based on production scenarios.
- Keep explicit inputs and safe defaults for each run.
- Attach checks to self-hosted preflight.
- Set baseline tags and add optional steps progressively after validation.
- Require run notes on every change for full audit trail.
Integration points
- Preflight as mandatory step before important changes.
- First run as baseline validation of stack and flow.
- Self-hosted governance for role and scope standards.
- Runbook for long-term evidence and retrospectives.
Handling exceptions
- Emergency changes should be marked, reviewed, and converted into standard templates when stable.
- Emergency paths must include explicit reason and follow-up evidence.
Next step: Validate access model in self-hosted workspace and security or move to routine in self-hosted day-to-day operations.