Forge and Vapor deployment in Laravel - Mini Project: Build & Apply

Deploying a Laravel App with Forge and Vapor

📖 Scenario: You have built a Laravel web application and want to deploy it to the cloud. You will use Laravel Forge to set up a server and Laravel Vapor to deploy a serverless version of your app.

🎯 Goal: Learn how to prepare your Laravel app for deployment, configure Forge and Vapor, and deploy your app successfully.

📋 What You'll Learn

Create a Laravel project with a basic route

Set up environment variables for deployment

Configure Forge server deployment settings

Configure Vapor deployment settings

💡 Why This Matters

🌍 Real World

Deploying Laravel applications to cloud servers and serverless platforms is common in modern web development to ensure scalability and reliability.

💼 Career

Understanding Forge and Vapor deployment prepares you for roles involving Laravel app deployment, DevOps tasks, and cloud infrastructure management.

1

Create a basic Laravel route

Create a Laravel route in routes/web.php that returns the string 'Hello from Laravel!' when visiting the root URL '/'.

Laravel

<?php

use Illuminate\Support\Facades\Route;

// Add a route for '/' that returns 'Hello from Laravel!'
// Your code here

Hint

Use Route::get with '/' as the path and a closure returning the string.

2

Set environment variables for deployment

Create a .env file in your Laravel project root with these exact entries:
APP_NAME=LaravelApp
APP_ENV=production
APP_DEBUG=false
APP_URL=https://yourdomain.com

Laravel

<?php

use Illuminate\Support\Facades\Route;

Route::get('/', function () {
    return 'Hello from Laravel!';
});

// Create a .env file with deployment variables
// Your code here

Hint

The .env file holds configuration for your app environment. Use the exact keys and values given.

3

Configure Forge deployment script

In your Forge server deployment script, add the command php artisan migrate --force to run database migrations automatically after deployment.

Laravel

<?php

use Illuminate\Support\Facades\Route;

Route::get('/', function () {
    return 'Hello from Laravel!';
});

// Add deployment script command to run migrations
// Your code here

Hint

Use the exact command php artisan migrate --force in your Forge deployment script to apply migrations safely.

4

Add Vapor deployment configuration

In your vapor.yml file, add the environments section with production environment setting memory: 1024 and timeout: 60 to configure Vapor deployment resources.

Laravel

<?php

use Illuminate\Support\Facades\Route;

Route::get('/', function () {
    return 'Hello from Laravel!';
});

// Add vapor.yml environments configuration
// Your code here

Hint

Use the exact keys environments, production, memory, and timeout with the given values in vapor.yml.

Practice

1. What is the main difference between Laravel Forge and Laravel Vapor?

easy

A. Forge is a code editor, Vapor is a testing tool

B. Forge is for database management, Vapor is for caching

C. Forge only works with Windows, Vapor only with Linux

D. Forge deploys to traditional servers, Vapor deploys to serverless cloud

Solution

1. Step 1: Understand Forge's deployment method

   Forge is designed to deploy Laravel applications on traditional servers like VPS or dedicated machines.

2. Step 2: Understand Vapor's deployment method

   Vapor deploys Laravel applications to serverless cloud platforms, such as AWS Lambda, removing the need to manage servers.

3. Final Answer:

   Forge deploys to traditional servers, Vapor deploys to serverless cloud -> Option D

4. Quick Check:

   Deployment type difference = A [OK]

Hint: Forge = servers, Vapor = serverless cloud deployment [OK]

Common Mistakes:

• Confusing Forge as a database tool
• Thinking Vapor is a code editor
• Mixing up operating system support

2. Which of the following is the correct command to deploy a Laravel app using Vapor?

easy

A. vapor start production

B. vapor deploy production

C. php artisan vapor:deploy

D. forge deploy production

Solution

1. Step 1: Recall Vapor CLI commands

   The official Vapor CLI uses the command vapor deploy [environment] to deploy applications.

2. Step 2: Check other options for correctness

   forge deploy is not a Vapor command, php artisan vapor:deploy is invalid, and vapor start is not a deploy command.

3. Final Answer:

   vapor deploy production -> Option B

4. Quick Check:

   Vapor deploy command = D [OK]

Hint: Vapor deploy uses 'vapor deploy environment' command [OK]

Common Mistakes:

• Using forge commands with Vapor
• Trying artisan commands for Vapor deployment
• Using 'start' instead of 'deploy'

3. Given this Forge deployment script snippet:

cd /home/forge/example.com
git pull origin main
composer install --no-dev
php artisan migrate --force
php artisan config:cache

What is the purpose of php artisan migrate --force in this context?

medium

A. It runs database migrations without asking for confirmation

B. It clears the cache before deployment

C. It installs composer dependencies

D. It restarts the web server

Solution

1. Step 1: Understand the migrate command

   php artisan migrate runs database migrations to update the schema.

2. Step 2: Understand the --force flag

   The --force flag runs migrations in production without interactive confirmation.

3. Final Answer:

   It runs database migrations without asking for confirmation -> Option A

4. Quick Check:

   Migration with --force = B [OK]

Hint: --force runs migrations silently in production [OK]

Common Mistakes:

• Thinking migrate clears cache
• Confusing migrate with composer install
• Assuming migrate restarts server

4. You try to deploy with Vapor but get an error: Could not find AWS credentials. What is the most likely cause?

medium

A. AWS credentials are not configured in Vapor environment settings

B. Laravel version is incompatible with Vapor

C. Composer dependencies are missing

D. Forge server is offline

Solution

1. Step 1: Analyze the error message

   The error indicates missing AWS credentials, which Vapor requires to deploy to AWS services.

2. Step 2: Identify the cause

   If AWS credentials are not set in Vapor's environment or CLI config, deployment fails with this error.

3. Final Answer:

   AWS credentials are not configured in Vapor environment settings -> Option A

4. Quick Check:

   Missing AWS credentials = C [OK]

Hint: Check AWS credentials setup in Vapor config [OK]

Common Mistakes:

• Blaming Laravel version for AWS errors
• Assuming composer issues cause AWS errors
• Confusing Forge server status with Vapor errors

5. You want to deploy a Laravel app using Forge and ensure zero downtime during deployment. Which approach should you take?

hard

A. Deploy with Vapor instead of Forge for zero downtime

B. Manually stop the server, deploy code, then start the server again

C. Use Forge's deployment hooks to run migrations and cache commands after code update

D. Skip migrations during deployment to avoid downtime

Solution

1. Step 1: Understand Forge deployment hooks

   Forge allows running scripts after code is updated, such as migrations and cache clearing, without stopping the server.

2. Step 2: Why this ensures zero downtime

   Running migrations and cache commands in hooks keeps the app live and updated smoothly, avoiding downtime.

3. Step 3: Evaluate other options

   Stopping the server causes downtime, Vapor is a different platform, and skipping migrations risks data inconsistency.

4. Final Answer:

   Use Forge's deployment hooks to run migrations and cache commands after code update -> Option C

5. Quick Check:

   Forge hooks for zero downtime = A [OK]

Hint: Use Forge hooks to run commands after deploy for zero downtime [OK]

Common Mistakes:

• Stopping server causes downtime
• Skipping migrations breaks database
• Confusing Vapor with Forge deployment methods