Forge and Vapor deployment in Laravel - Step-by-Step Execution

Concept Flow - Forge and Vapor deployment

Start: Prepare Laravel app

↓

Choose deployment method

↓

Forge Deployment

↓

Provision Server

↓

Deploy Code

↓

Run Migrations

↓

App Live on Server

↓

Monitor & Maintain

This flow shows the steps from preparing a Laravel app to deploying it either on a Forge-managed server or on AWS using Vapor, ending with monitoring.

Execution Sample

Laravel

forge deploy --server=123
vapor deploy production

Commands to deploy a Laravel app using Forge and Vapor respectively.

Execution Table

Step	Action	Tool/Command	Result	Next Step
1	Prepare Laravel app code	N/A	App ready for deployment	Choose deployment method
2	Select deployment method	User choice	Forge or Vapor selected	Provision server or configure AWS
3	Provision server (Forge)	Forge UI/API	Server ready with PHP, DB	Deploy code to server
4	Configure AWS (Vapor)	Vapor CLI & AWS Console	AWS environment ready	Deploy serverless app
5	Deploy code (Forge)	forge deploy --server=123	Code pushed to server	Run migrations
6	Deploy serverless app (Vapor)	vapor deploy production	App deployed on AWS Lambda	Run migrations
7	Run migrations	php artisan migrate	Database updated	App live
8	App live	N/A	App accessible to users	Monitor & maintain
9	Monitor & maintain	Forge/Vapor dashboards	App health monitored	Repeat deploys as needed
10	Exit	N/A	Deployment cycle complete	End

💡 Deployment cycle ends after app is live and monitored

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 7	Final
Server Status	Not provisioned	Provisioned	Code deployed	Migrations run	Live and monitored
AWS Environment	Not configured	Configured	App deployed	Migrations run	Live and monitored
App Code	Prepared	Prepared	Deployed	Deployed	Running live

Key Moments - 3 Insights

Why do we need to run migrations after deploying code?

Running migrations updates the database structure to match the app code, as shown in step 7 of the execution_table.

What is the difference between provisioning a server in Forge and configuring AWS in Vapor?

Provisioning in Forge sets up a traditional server with PHP and database, while Vapor configures a serverless AWS environment, as seen in steps 3 and 4.

Can we deploy the app without choosing a deployment method?

No, choosing Forge or Vapor determines the deployment process, as shown in step 2 where the flow splits.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 5?

A Code is deployed to the Forge server

B AWS environment is configured

C Migrations are run

D App is live and monitored

💡 Hint

Check the 'Action' and 'Result' columns for step 5 in the execution_table

At which step does the app become accessible to users?

A Step 7

B Step 8

C Step 3

D Step 10

💡 Hint

Look for 'App live' in the 'Action' column in the execution_table

If we skip provisioning the server in Forge, what will happen?

A Migrations will run successfully

B App will be live immediately

C Code deployment will fail

D AWS environment will be used instead

💡 Hint

Refer to step 3 and 5 in the execution_table to see the dependency

Concept Snapshot

Forge and Vapor deployment:
- Prepare Laravel app
- Choose Forge (server) or Vapor (serverless AWS)
- Provision server or configure AWS
- Deploy code or serverless app
- Run migrations to update DB
- App goes live and monitored
- Repeat deploys as needed

Full Transcript

This visual execution shows how to deploy a Laravel app using Forge or Vapor. First, you prepare your app code. Then you choose your deployment method: Forge for traditional servers or Vapor for serverless AWS. Forge requires provisioning a server with PHP and database, while Vapor configures AWS Lambda and related services. Next, you deploy your code using forge deploy or vapor deploy commands. After deployment, you run database migrations to update the schema. Once migrations complete, the app becomes live and accessible to users. Finally, you monitor the app health using Forge or Vapor dashboards and repeat deployments as needed. This step-by-step flow helps beginners understand the deployment lifecycle clearly.

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