Application Deployment

CtrlOps provides a streamlined deployment engine designed to bridge the gap between your local development and production environments. It supports Git-based synchronization and automated build pipelines for modern web stacks.

Deployment Lifecycle

Every deployment in CtrlOps follows a structured 4-stage lifecycle to ensure consistency and minimize downtime.

1. Git Synchronization

CtrlOps connects to your remote repositories (GitHub, GitLab, Bitbucket) and pulls the latest changes to a staging directory:

git pull origin main

2. Dependency & Build Phase

Depending on your application type, CtrlOps executes the appropriate build commands:

npm install --production
npm run build

python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

docker build -t your-app:latest .
docker stop old-container && docker rm old-container
docker run -d --name old-container your-app:latest

3. Production cut-over

For traditional file-based deployments, CtrlOps can use rsync or symbolic link swapping to switch the production traffic to the new build artifact with minimal interruption.

Deployment Configuration

You can configure your deployment settings per-project:

Best Practices

• Environment Variables: Manage your .env files through the File Manager before deploying.
• Health Checks: Always verify your application status in the Infra Details view after a fresh deployment.
• Rollbacks: Keep previous build directories to allow for rapid rollbacks if a deployment fails.