3

Deploying application updates manually can be time-consuming, especially when managing multiple websites or production environments. Uploading files, verifying changes, and coordinating releases often introduce delays and increase the risk of deployment errors.

RunCloud simplifies this process with built-in deployment automation tools that allow developers and server administrators to deploy code directly from Git repositories. Combined with Atomic Deployment, RunCloud helps ensure smooth releases, minimal downtime, and reliable rollback options.

In this guide, we’ll explore how to automate deployments with RunCloud, configure Git integration, enable Atomic Deployment, and create a streamlined deployment workflow for your applications.

Why Automate Deployments?

Modern development teams rely on automation to deliver updates quickly and consistently. Manual deployment processes can lead to version mismatches, accidental file overwrites, and downtime during updates.

By automating deployments with RunCloud, you can benefit from:

-> Faster Releases

Code changes can be deployed directly from your Git repository, eliminating manual uploads and reducing deployment time.

-> Improved Consistency

Every deployment follows the same predefined workflow, reducing the likelihood of human error.

-> Zero-Downtime Updates

RunCloud’s Atomic Deployment feature ensures users continue accessing the previous stable version while a new release is prepared.

-> Simplified Team Collaboration

Developers can push code through Git without requiring direct server access, improving both productivity and security.

-> Easier Rollbacks

If a deployment encounters issues, previous releases remain available and can be restored quickly.

Prerequisites Before You Begin

Before setting up automated deployments in RunCloud, make sure you have:

• An active RunCloud account
• A server connected to RunCloud
• A web application configured in RunCloud
• A Git repository hosted on GitHub, GitLab, Bitbucket, or another supported platform
• SSH authentication configured between your repository and server

Having these components ready will make the deployment setup process much smoother.

Step 1: Connect Your Git Repository to RunCloud

RunCloud allows direct integration with Git repositories, enabling automatic code deployments whenever updates are pushed.

Enable Git Deployment

1. Log in to your RunCloud dashboard.
2. Navigate to Web Applications.
3. Select the application you want to automate.
4. Open the Git tab.
5. Click Enable Git Deployment.

Configure Repository Details

Next, provide:

• Repository URL
• Deployment branch (such as main, master, or production)
• Git provider information

Supported providers include:

• GitHub
• GitLab
• Bitbucket
• Custom Git repositories

Configure SSH Authentication

RunCloud generates an SSH key for secure repository access.

To complete authentication:

1. Copy the SSH public key displayed in RunCloud.
2. Add the key to your Git provider.
3. Verify repository access.

Once configured, RunCloud can securely pull updates from your repository whenever a deployment is triggered.

Step 2: Enable Atomic Deployment

One of the most valuable deployment features in RunCloud is Atomic Deployment.

Traditional deployment methods replace files directly in the live application directory, which can cause downtime if something goes wrong during deployment.

Atomic Deployment eliminates this risk.

How Atomic Deployment Works

Instead of updating files directly:

• A new release directory is created.
• Application files are deployed to the new release.
• Validation checks are performed.
• A symbolic link is updated only after deployment succeeds.
• Previous releases remain available for rollback.

This process ensures users always access a stable version of the application.

Enable Atomic Deployment in RunCloud

To enable the feature:

1. Open your web application dashboard.
2. Navigate to the Git section.
3. Locate the Atomic Deployment settings.
4. Click Deploy a Project.
5. Enable Atomic Deployment.

After activation, every deployment follows the atomic release process automatically.

Benefits of Atomic Deployment

– Zero Downtime

Visitors continue accessing the active release until the new version is fully deployed and verified.

– Automatic Rollback Protection

If a deployment fails, RunCloud automatically retains the previous working version.

– Safer Production Deployments

Changes are isolated from the live application until deployment is completed successfully.

– Easier Troubleshooting

Multiple release versions remain available, making it easier to compare deployments and identify issues.

Step 3: Test Your Automated Deployment Workflow

Once Git integration and Atomic Deployment are configured, it’s important to verify everything works correctly.

Create a Test Update

Make a small change in your application repository and push it to the deployment branch.

For example:

• Update a page title
• Modify a configuration file
• Change application content

Verify Deployment

After pushing changes:

1. Monitor the deployment process in RunCloud.
2. Confirm the latest commit appears in deployment logs.
3. Visit your website or application.
4. Verify that the changes are visible.

If everything is configured correctly, RunCloud will automatically fetch the latest code and deploy the update.

Best Practices for RunCloud Deployment Automation

To maximize reliability and security, follow these deployment best practices.

> Use Dedicated Deployment Branches

Separate development and production workflows by maintaining dedicated deployment branches.

Examples include:

• Development
• Staging
• Production

This reduces the risk of unintended code reaching live environments.

> Review Code Before Deployment

Implement pull request reviews and testing procedures before merging code into production branches.

> Monitor Deployment Logs

Regularly review deployment logs to identify:

• Failed deployments
• Permission issues
• Repository access problems
• Application errors

> Keep Dependencies Updated

Ensure your application dependencies and server packages remain current to avoid deployment conflicts.

> Maintain Rollback Procedures

Even with Atomic Deployment, administrators should have documented rollback plans for critical applications.

Why RunCloud Deployment Automation Matters

As websites and applications grow, deployment complexity increases. Automating deployments allows teams to focus on development instead of spending valuable time performing repetitive server tasks.

With Git integration and Atomic Deployment, RunCloud provides:

• Faster software releases
• Improved deployment reliability
• Enhanced security
• Reduced operational overhead
• Better collaboration between development and operations teams

Whether you’re managing a single website or multiple production servers, deployment automation helps create a more efficient workflow.

Conclusion

Automating deployments with RunCloud is one of the easiest ways to improve application delivery speed, consistency, and reliability. By integrating Git repositories and enabling Atomic Deployment, you can deploy updates with confidence while minimizing downtime and reducing the risk of human error.

A well-configured automated deployment process ensures your applications remain stable, your development workflow stays efficient, and your users enjoy a seamless experience every time new updates are released.

Simplify Your RunCloud Management with SupportPRO

Managing deployments, servers, Git integrations, and production environments can become challenging as your infrastructure grows.

Contact SupportPRO today for expert RunCloud management, deployment automation, and server administration services.