Overview
Deployments provide a comprehensive view of your site’s deployment history, allowing you to track changes, monitor deployment status, and rollback to previous versions when needed. Loupp automatically tracks all deployments with detailed logging and status monitoring.Deployment History Interface
Overview Dashboard
The deployments interface displays comprehensive deployment information:Deployment Info
- Deployment timestamp and duration
- Commit details and branch information
- Current deployment status
Source Control
- Repository and branch details
- Commit hash and message
- Links to source control platforms
Status Tracking
- Real-time deployment status
- Success/failure indicators
- Time tracking for active deployments
Deployment Table Structure
The deployment history table provides detailed information for each deployment:Deployment Information
Deployment Information
- Timestamp: When the deployment was initiated
- Duration: How long the deployment took
- Status: Current deployment state
- Latest/Current Indicators: Special badges for active deployments
Source Control Details
Source Control Details
- Branch: Deployment branch name
- Commit Hash: Shortened commit identifier
- Commit Message: Descriptive message about changes
- Platform Links: Direct links to GitHub/GitLab.
Performance Metrics
Performance Metrics
- Time Taken: Actual deployment duration
- Status Indicators: Visual status representations
- Action Buttons: Available operations for each deployment
Deployment Status Tracking
Status Indicators
Deployments progress through different statuses:Running
Deployment is currently in progress
Finished
Deployment completed successfully
Failed
Deployment encountered an error
Rolled Back
Deployment was reverted to previous version
Rollback Management
Rollback Capabilities
Rollback allows you to revert to previous deployment versions:Rollback Requirements
Rollback Requirements
- Site must be in “active” status
- Previous deployment must exist
- No active deployments running
- Sufficient disk space for rollback
Rollback Process
Rollback Process
- System automatically switches to previous version
- Database changes may need manual handling
- Environment variables are preserved
- SSL certificates remain active
Performing Rollbacks
1
Identify target version
Select the deployment version you want to rollback to.
2
Initiate rollback
Click “Rollback To This Version” from the deployment actions menu.
3
Confirm action
Review the confirmation dialog and confirm the rollback.
4
Monitor process
Track rollback progress and verify completion.
Rollbacks can result in data loss if the previous version had different database schemas or configurations.
Deployment Management Features
Deployment Actions
Each deployment entry provides specific actions:View Logs
View Logs
Purpose: Access detailed deployment execution logsUse Cases:
- Debug failed deployments
- Verify successful deployments
- Monitor deployment performance
- Troubleshoot issues
Rollback
Rollback
Purpose: Revert to previous deployment versionUse Cases:
- Fix critical issues quickly
- Revert problematic changes
- Restore stable versions
- Emergency recovery
Deployment Indicators
Special badges help identify important deployments:Latest Badge
Most recent deployment from the repository
Current Badge
Currently active deployment on the server