Local disk storage in Laravel - Step-by-Step Execution

Concept Flow - Local disk storage

Start: Request to store file

↓

Call Storage facade with disk 'local'

↓

Check if 'local' disk is configured

↓

Save file to storage/app directory

↓

Return file path or success response

↓

End

This flow shows how Laravel stores a file on the local disk by calling the Storage facade, checking configuration, saving the file, and returning the path.

Execution Sample

Laravel

use Illuminate\Support\Facades\Storage;

$filePath = Storage::disk('local')->put('example.txt', 'Hello Laravel!');

return $filePath;

This code saves a text file named 'example.txt' with content 'Hello Laravel!' to the local disk and returns the saved file path.

Execution Table

Step	Action	Disk Selected	File Path	Result
1	Call Storage::disk('local')	local	N/A	Disk instance ready
2	Put file 'example.txt' with content	local	example.txt	File saved in storage/app/example.txt
3	Return file path	local	example.txt	example.txt returned

💡 File saved successfully on local disk, path returned

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
$filePath	null	null	true	true

Key Moments - 3 Insights

Why do we specify 'local' in Storage::disk('local')?

Because Laravel supports multiple disks, specifying 'local' tells it to use the local filesystem configured in config/filesystems.php. See execution_table step 1.

Where is the file actually saved on the server?

The file is saved inside the storage/app directory by default when using the 'local' disk. This is shown in execution_table step 2.

What does the put() method return?

The put() method returns true on success or false on failure, not the file path. To get the file path, you use the path or url methods. See Laravel documentation.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of $filePath after step 2?

A true

B null

C 'example.txt'

D 'storage/app/example.txt'

💡 Hint

The put() method returns true on success, not the file path.

At which step does Laravel confirm the file is saved on disk?

A Step 1

B Step 3

C Step 2

D No confirmation step

💡 Hint

Look at the 'Result' column in execution_table for Step 2

If you change 'local' to 'public' in Storage::disk('local'), what changes in the execution?

A File saves to storage/app directory

B File saves to storage/app/public directory

C File saves to root directory

D File is not saved

💡 Hint

Recall that 'public' disk points to storage/app/public, different from 'local' disk

Concept Snapshot

Laravel Local Disk Storage:
- Use Storage::disk('local') to select local disk
- put('filename', content) saves file in storage/app
- Returns true on success
- Configured in config/filesystems.php
- Default local disk stores files privately

Full Transcript

This lesson shows how Laravel stores files on the local disk using the Storage facade. First, the code calls Storage::disk('local') to select the local disk configured in the application. Then, it uses the put method to save a file named 'example.txt' with the content 'Hello Laravel!' inside the storage/app directory. The put method returns true on success. This process ensures files are saved privately on the server's local filesystem. The execution table traces each step, showing the disk selection, file saving, and returned status. Variables like $filePath update accordingly. Key points include why specifying the disk matters, where files are saved, and what put returns. The quiz tests understanding of these steps and effects of changing disks. This helps beginners see exactly how Laravel handles local file storage step-by-step.

Practice

1. What does the local disk in Laravel's storage system refer to?

easy

A. A remote FTP server

B. A cloud storage service like AWS S3

C. A temporary cache in memory

D. The server's own hard drive inside storage/app

Solution

1. Step 1: Understand Laravel's local disk meaning

   The local disk stores files on the server's hard drive, specifically inside the storage/app directory.

2. Step 2: Compare with other storage options

   Other options like cloud or FTP are not called local. The local disk is always the server's own storage.

3. Final Answer:

   The server's own hard drive inside storage/app -> Option D

4. Quick Check:

   Local disk = server hard drive storage [OK]

Hint: Local disk means server's own storage folder [OK]

Common Mistakes:

• Confusing local disk with cloud storage
• Thinking local disk is temporary memory
• Assuming local disk is remote storage

2. Which of the following is the correct syntax to save a file named example.txt with content 'Hello' on the local disk in Laravel?

easy

A. Storage::disk('example.txt')->put('local', 'Hello');

B. Storage::disk('local')->put('example.txt', 'Hello');

C. Storage::put('local', 'example.txt', 'Hello');

D. Storage::local()->put('example.txt', 'Hello');

Solution

1. Step 1: Identify correct method chaining

   Laravel uses Storage::disk('local')->put(filename, content) to save files on the local disk.

2. Step 2: Check method and parameter order

   Storage::disk('local')->put('example.txt', 'Hello'); correctly calls disk('local') then put('example.txt', 'Hello'). Others mix parameters or methods incorrectly.

3. Final Answer:

   Storage::disk('local')->put('example.txt', 'Hello'); -> Option B

4. Quick Check:

   Use disk('local')->put(filename, content) [OK]

Hint: Use Storage::disk('local')->put(filename, content) [OK]

Common Mistakes:

• Swapping parameters in put method
• Calling disk() with filename instead of 'local'
• Using Storage::local() which does not exist

3. What will be the output of this Laravel code snippet?

Storage::disk('local')->put('note.txt', 'Hi there');
$content = Storage::disk('local')->get('note.txt');
echo $content;

medium

A. Hi there

B. note.txt

C. Storage::disk('local')->put

D. File not found error

Solution

1. Step 1: Save content to local disk

   The put method writes 'Hi there' into 'note.txt' on the local disk.

2. Step 2: Retrieve and echo the file content

   The get method reads the content of 'note.txt', which is 'Hi there', then echoes it.

3. Final Answer:

   Hi there -> Option A

4. Quick Check:

   Put then get returns saved content [OK]

Hint: put saves file, get reads content back [OK]

Common Mistakes:

• Expecting filename instead of content output
• Assuming get returns boolean
• Forgetting to use disk('local')

4. Identify the error in this Laravel code that tries to delete a file from local disk:

Storage::disk('local')->delete('file.txt');

Assuming file.txt does not exist, what happens?

medium

A. Returns false but no exception is thrown

B. Deletes all files in the local disk

C. Creates an empty file named file.txt

D. Throws an exception and stops execution

Solution

1. Step 1: Understand delete behavior on missing files

   Laravel's delete method returns false if the file does not exist but does not throw an error.

2. Step 2: Confirm no side effects

   No file is created or deleted besides the target. Execution continues normally.

3. Final Answer:

   Returns false but no exception is thrown -> Option A

4. Quick Check:

   Delete missing file returns false, no error [OK]

Hint: Delete returns false if file missing, no crash [OK]

Common Mistakes:

• Expecting an exception on missing file
• Thinking delete creates files
• Assuming delete removes all files

5. You want to save a user-uploaded image on the local disk with a unique name to avoid overwriting. Which Laravel code snippet correctly achieves this?

hard

A. Storage::disk('local')->put('image.jpg', $imageContent);

B. Storage::disk('local')->putFileAs('', $imageFile, 'image.jpg');

C. Storage::disk('local')->putFile('', $imageFile);

D. Storage::disk('local')->put('image.jpg', $imageFile);

Solution

1. Step 1: Understand putFile and putFileAs methods

   putFile stores the file with a unique generated name automatically. putFileAs requires you to specify the filename.

2. Step 2: Check options for unique naming

   Storage::disk('local')->putFile('', $imageFile); uses putFile which auto-generates a unique name, preventing overwrites. The distractors use fixed filenames such as 'image.jpg', which risk overwriting existing files.

3. Final Answer:

   Storage::disk('local')->putFile('', $imageFile); -> Option C

4. Quick Check:

   putFile auto-names files uniquely [OK]

Hint: Use putFile to auto-generate unique file names [OK]

Common Mistakes:

• Using put which overwrites files
• Manually generating names incorrectly
• Using putFileAs without unique names