How to run your first deployment
The biggest benefit of LaraDep shows up when your first deployment works correctly — without lengthy documentation searches and without repeating mistakes. To get there, you need clarity on a few things before you start.
What to prepare in advance
- A server or VPS — IP address and SSH access (key or password).
- Template values — domain name, database password, and other fields the template requires (the wizard will show you what is needed).
Step-by-step process
- Create a workspace — a workspace is your context for a group of servers or clients.
- Add a server — enter the IP address and credentials. LaraDep verifies the connection.
- Pick a template — each template describes what it sets up. Choose the one that matches your intention.
- Fill in the form — every field is described, no guessing.
- LaraDep runs preflight checks — verifies that values are complete and the server is reachable.
- Watch the progress — every step is visible in real time.
- Review the outcome — the result is recorded in the workspace history.
Production checklist
A production deployment is different from a test deployment. Go through this checklist before running a deployment to production.
Server and connection
- The server is reachable and SSH credentials are correct.
- The server has sufficient resources (disk, RAM).
Backups
- You have a backup of the current server state if this is an existing server.
- A database backup is current.
- You know how to restore the backup if the deployment fails.
Values and settings
- All values in the template form are for production — not test values.
- The domain name matches the production domain.
- Passwords are strong and securely stored in the workspace.
- An SSL certificate is ready or will be configured as part of the deployment.
Workspace and access
- The server is in the correct workspace — the deployment will target the right servers.
- Team members have the correct roles.
- You know who is monitoring the deployment.
After the deployment
- Verify that the website or application is working correctly.
- Check the deployment record in the workspace history.
Where issues most often appear
- The server is unreachable or SSH credentials are wrong — LaraDep catches this during preflight.
- A required form value is missing — LaraDep notifies you before starting.
- The template does not fit — pick a different one or contact us at pavelzanek.com/en.
For teams
Add colleagues to the workspace and set their roles — who can run deployments and who can only view history. Every deployment is recorded with the name of the user who ran it.
Next step: Continue with the runbook and governance page.