Self-hosted day-to-day operations

Self-hosted day-to-day operations

Self-hosted mode gives broad flexibility, but it requires a clear operating rhythm. This page defines how to keep each change planned, traceable, and repeatable.

Purpose and audience

For teams running LaraDep on their own infrastructure and wanting predictable operations rather than ad-hoc changes.

Before deployment

• Confirm the workspace is set up correctly and team roles are assigned.
• Check that the template and all required variables are ready before starting.
• Ensure communication channels are ready for planned changes and incidents.

Operational run routine

1. Define the change: what changes, which servers, who approves it.
2. Run guided flow: fill in input values and pass preflight validation.
3. Watch progress in real time: monitor steps and stop adding extra actions while a run is failing.
4. Validate after completion: check target service availability, DNS and TLS configuration.
5. Close the run: confirm record status in workspace history and add notes when needed.

Operational checklist

• Is each deployment validated through preflight before start?
• Is there a clear change owner and approver before execution?
• Were critical services verified after completion?
• Is rollback available and communicated?
• Is the deployment record complete with context?

Common mistakes

• Running deployments without a defined approver role.
• Deployment outside planned windows without team notification.
• Stopping a run without documenting impact and follow-up action.
• Relying on memory instead of recorded evidence.

Next steps

• For first-time deployments, follow First deployment and production checklist.
• For standardized sequence and checks, use Templates and workflow.
• For long-term governance and auditability, use Runbook and governance.
• For incident handling and restoration, use Troubleshooting and incident response.

Next step: Browse the documentation or contact us.