Do I need to commit .gitignore?

Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.

How do I add custom patterns?

Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.

How do I ignore a file that is already tracked?

Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached to stop tracking it without deleting the file locally.

Should I commit .env?

Never commit .env. Commit .env.example with placeholder values. Never put real secrets in version control.

.gitignore for Laravel

Laravel vendor directory, .env secrets, storage uploads, and bootstrap cache.

Quick presets

Selected (1)

Laravel

Your selections never leave your browser. Generation happens entirely client-side.

Raw

14 patterns · 353 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Laravel
# 2026-04-20

# ---- Laravel ----
# Laravel
/vendor/
node_modules/
/public/hot
/public/storage
/storage/*.key
.env
.env.backup
.env.production
.phpunit.result.cache
Homestead.json
Homestead.yaml
auth.json
/bootstrap/cache/*
!/bootstrap/cache/.gitkeep

What this template ignores

Ignores the Composer vendor/ directory, .env secrets, storage keys, bootstrap cache, and Homestead VM configuration.

Common additions

+storage/logs/ — Laravel log files (large in production)
+_ide_helper.php — Laravel IDE helper generated file

Commonly paired with

php composer node Combine →

Frequently asked questions

Do I need to commit .gitignore?: Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?: Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?: Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Should I commit .env?: Never commit .env. Commit .env.example with placeholder values. Never put real secrets in version control.

Looking for something else? Browse all templates →