First Laravel application - Step-by-Step Execution

Concept Flow - First Laravel application

Install Laravel

↓

Create Project Folder

↓

Run Development Server

↓

Open Browser

↓

See Welcome Page

↓

Modify Route

↓

Refresh Browser

↓

See Custom Message

This flow shows the steps to create and run your first Laravel app, from installation to seeing your custom page in the browser.

Execution Sample

Laravel

php artisan serve

// In routes/web.php
Route::get('/', function () {
    return 'Hello, Laravel!';
});

Starts Laravel server and sets a route to show a simple greeting on the homepage.

Execution Table

Step	Action	File/Command	Result/Output
1	Install Laravel via Composer	composer create-project laravel/laravel myapp	Laravel project created in 'myapp' folder
2	Navigate to project folder	cd myapp	Ready to run server
3	Start development server	php artisan serve	Server running at http://127.0.0.1:8000
4	Open browser at server URL	http://127.0.0.1:8000	Laravel welcome page displayed
5	Edit route in routes/web.php	Route::get('/', function () { return 'Hello, Laravel!'; });	Homepage route returns custom text
6	Refresh browser	http://127.0.0.1:8000	Page shows 'Hello, Laravel!'
7	Stop server	Ctrl+C	Server stopped
8	Exit	-	End of session

💡 Server stopped and no further actions

Variable Tracker

Variable	Start	After Step 4	After Step 6	Final
Server Status	Stopped	Running	Running	Stopped
Route '/' Response	Default welcome page	Default welcome page	'Hello, Laravel!'	'Hello, Laravel!'

Key Moments - 3 Insights

Why does the browser show the default Laravel welcome page before changing the route?

Because before editing routes/web.php, Laravel uses its default route which shows the welcome page (see execution_table step 4).

What happens when you refresh the browser after changing the route?

The browser requests the homepage again, and Laravel returns the new response defined in routes/web.php (execution_table step 6).

Why do we need to stop the server with Ctrl+C?

Because 'php artisan serve' runs a local server process that keeps running until manually stopped (execution_table step 7).

Visual Quiz - 3 Questions

Look at the execution table, what is the server status after step 4?

A Stopped

B Running

C Starting

D Unknown

💡 Hint

Check the 'Server Status' variable in variable_tracker after step 4

At which step does the homepage start showing 'Hello, Laravel!'?

A Step 4

B Step 5

C Step 6

D Step 7

💡 Hint

Look at execution_table rows for browser refresh and output

If you do not run 'php artisan serve', what will happen when you open the browser at http://127.0.0.1:8000?

A Browser shows error or cannot connect

B Laravel welcome page shows

C Custom route message shows

D Page loads slowly

💡 Hint

Check execution_table step 3 where server starts before browser can connect

Concept Snapshot

First Laravel Application Quick Steps:
1. Install Laravel with Composer.
2. Navigate to project folder.
3. Run 'php artisan serve' to start server.
4. Open browser at http://127.0.0.1:8000.
5. Edit routes/web.php to change homepage.
6. Refresh browser to see changes.
7. Stop server with Ctrl+C.

Full Transcript

To create your first Laravel application, you start by installing Laravel using Composer. Then you go into the project folder and run the built-in server with 'php artisan serve'. Opening the browser at the server address shows the default Laravel welcome page. You can change what the homepage shows by editing the route in routes/web.php. After saving, refreshing the browser shows your custom message. When done, stop the server with Ctrl+C. This process helps you see how Laravel serves pages and how routing works.

Practice

1. What is the main purpose of the routes/web.php file in a new Laravel application?

easy

A. To configure server settings for deployment

B. To store database connection settings

C. To write CSS styles for the application

D. To define the URLs and what they should return when visited

Solution

1. Step 1: Understand the role of routes in Laravel

   Routes tell Laravel which URL should show which content or run which code.

2. Step 2: Identify what routes/web.php does

   This file is where you write those URL rules for web pages.

3. Final Answer:

   To define the URLs and what they should return when visited -> Option D

4. Quick Check:

   Routes = URL rules [OK]

Hint: Routes file maps URLs to responses [OK]

Common Mistakes:

• Confusing routes with database settings
• Thinking routes handle CSS or server configs
• Assuming routes are for backend logic only

2. Which command starts the built-in Laravel development server?

easy

A. php artisan serve

B. php serve artisan

C. php artisan start

D. php start artisan

Solution

1. Step 1: Recall the Laravel command to run the server

   The correct command is php artisan serve to start the local server.

2. Step 2: Check the options for correct syntax

   Only php artisan serve matches the exact command syntax.

3. Final Answer:

   php artisan serve -> Option A

4. Quick Check:

   Start server = php artisan serve [OK]

Hint: Remember: 'serve' runs the server in Laravel [OK]

Common Mistakes:

• Swapping command order
• Using 'start' instead of 'serve'
• Adding extra words in the command

3. Given this route in routes/web.php:

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

What will you see when you visit http://localhost:8000/ in your browser?

medium

A. A blank page

B. An error message

C. The text 'Hello, Laravel!'

D. A JSON object

Solution

1. Step 1: Understand the route definition

   The route listens for a GET request at '/' and returns the string 'Hello, Laravel!'.

2. Step 2: Predict the browser output

   Visiting the root URL will display exactly the returned string as plain text.

3. Final Answer:

   The text 'Hello, Laravel!' -> Option C

4. Quick Check:

   Route returns string = 'Hello, Laravel!' [OK]

Hint: Route returns string shown in browser [OK]

Common Mistakes:

• Expecting JSON or HTML page instead of plain text
• Thinking it shows an error or blank page
• Confusing route URL with different path

4. What is wrong with this route code in routes/web.php?

Route::get('/', function {
    return 'Welcome!';
});

medium

A. Missing semicolon after return statement

B. Missing parentheses after function keyword

C. Route method should be post, not get

D. The string should be in double quotes

Solution

1. Step 1: Check the function syntax

   Anonymous functions in PHP require parentheses even if no parameters are passed.

2. Step 2: Identify the syntax error

   The code misses parentheses after function, causing a syntax error.

3. Final Answer:

   Missing parentheses after function keyword -> Option B

4. Quick Check:

   Anonymous function needs () [OK]

Hint: Always add () after function for anonymous functions [OK]

Common Mistakes:

• Forgetting parentheses after function
• Thinking semicolon is missing after return
• Confusing HTTP methods get/post
• Believing string quotes cause error

5. You want to create a new Laravel route that returns the current year dynamically. Which code snippet correctly does this in routes/web.php?

hard

A. Route::get('/year', function () {
return date('Y');
});

B. Route::get('/year', function () {
echo "date('Y')";
});

C. Route::get('/year', function () {
return "Year is date('Y')";
});

D. Route::get('/year', function () {
return date(d);
});

Solution

1. Step 1: Use PHP date function correctly

   The date('Y') function returns the current year as a string.

2. Step 2: Return the year string properly in the route

   Using return date('Y'); inside the route's closure sends the year as response.

3. Step 3: Identify errors in other options

   The echo option outputs literal "date('Y')"; another returns literal "Year is date('Y')"; the last uses date(d) without quotes, returning the day of the month instead of the year.

4. Final Answer:

   Route::get('/year', function () { return date('Y'); }); -> Option A

5. Quick Check:

   Return date('Y') for current year [OK]

Hint: Use return with date('Y') inside route function [OK]

Common Mistakes:

• Using echo instead of return in route
• Forgetting quotes around 'Y' in date()
• Returning a string that does not evaluate PHP
• Confusing syntax for PHP date function