Deploying Feature Branches with Laravel Cloud: A Staging Guide

Overview of Laravel Cloud Staging

Maintaining a production application on a traditional server like

Laravel Forge
doesn't mean you can't utilize modern, serverless infrastructure for your development workflow.
Laravel Cloud
 provides a unique value proposition as a temporary staging environment. By isolating new features in dedicated environments, you can share live previews with stakeholders without touching your production stack or managing complex CI/CD pipelines for secondary servers.

Prerequisites

Before setting up your staging flow, ensure you have the following:

  • A
    GitHub
     account connected to your Laravel Cloud dashboard.
  • A
    Laravel
     application version-controlled with Git.
  • Basic familiarity with feature branching and terminal-based Git commands.

Key Libraries & Tools

  • Laravel Cloud: The primary platform for hosting serverless staging environments.
  • PHPStorm: A powerful IDE used for modifying the application code and managing commits.
  • GitHub: Handles the repository hosting and triggers automated deployments.

Code Walkthrough: From Branch to Deploy

1. Creating the Feature

First, isolate your changes. In this example, we implement a dark mode feature. After verifying the logic locally, commit your changes to a new branch.

# Create and switch to a new branch
git checkout -b feature/dark-mode

# Stage and commit changes
git add .
git commit -m "Implement dark mode feature"

# Push to GitHub
git push origin feature/dark-mode

2. Initial Application Setup

Navigate to the Laravel Cloud dashboard and select Create New Application. Choose your repository and preferred region. To keep costs minimal, immediately enable Hibernation. This ensures you only pay for processing time when the staging link is actively being visited.

3. Creating Environment Replicas

Once the main branch is deployed, you can create a "Replica" of your environment. This is the fastest way to test specific features.

  1. Click the three dots on your main environment.
  2. Select Copy Environment (Replica).
  3. Choose your feature branch (feature/dark-mode).

Laravel Cloud copies your environment variables and build scripts, deploying the branch in roughly 30 seconds.

Syntax Notes

Laravel Cloud simplifies environment management through its web interface, but the underlying mechanism relies on Git Branch Tracking. When you define a branch for a replica, the platform automatically maps that specific commit hash to a unique sub-domain, allowing for side-by-side comparison of different application states.

Practical Examples

  • Client Approvals: Send a unique URL to a client to approve a UI change before merging.
  • QA Testing: Deploy a replica for your testing team to verify a bug fix in an environment that mirrors production settings.

Tips & Gotchas

  • Enable Hibernation: Always toggle this on for staging to prevent unnecessary billing on idle environments.
  • Clean Up: Once a feature is merged, delete the environment under Settings > Delete Environment to keep your dashboard organized and ensure no residual costs occur.
3 min read