.gitignore what should be ignored?

Published 3 years ago by jasonb


What all should we be ignoring from the laravel 5 installation? .env composer.lock vendor

What about storage?

Anything else that may be a good idea/ -J

3 years ago (14,075 XP)

Hey Jason

First thing I see: do NOT ignore the composer.lock file, it's bad practice. For the explanation on this, I will refer you to a talk by Jordi Boggiano (creator of composer) on the subject - he can explain it much better than I can.

Here is a sample of the gitignore file I use on my projects. I won't claim that it's perfect, but it will get you started.











ok great. What do you think about storage/ ?

3 years ago (14,075 XP)

I would definitely add that in there. Now that you mention it, it's not in my .gitignore file, I'll have to change that ;-D

3 years ago (40,575 XP)

@jasonb , @Elimentz the directories under storage all already have the proper .gitignore in them so you don't need to add that to your root .gitignore.

If you add your own folder to storage, then just add a .gitignore in that directory:

3 years ago (1,002,700 XP)

Storage is added but nothing inside folders are included since they have .gitignore files in.


The storage folder you don't ignore, becouse in the folders has a .gitignore files, and you never push the storage files to the version controller.


Try this too :)


2 years ago (7,290 XP)

It does not make sense to me that, why should I ignore vendor folder? I hope someone already has this explanation.

2 years ago (39,025 XP)

@ruhul: the vendor folder contains all project dependencies, these are installed using "composer install" on a fresh project. No need to upload them to git since their version management is not within your project.

2 years ago (1,110 XP)

On the other hand, if you gitignore the vendor folder, you won't be able to use Git for deployment (push to your server to update your website) because you will have to install and run composer on your server, which might not be optimal, or even allowed on some hosting servers.

Plus, if some repository suddenly goes away from the Internet or is modified or corrupted (it happens) then you won't be able to run your project anymore.


@tobia I understand what you're saying but i would strongly recommend you do not use git for deployments. Git is a versioning tool and not a deploy tool. There are a lot of tools which are better suited for deployment. I myself use Ansible for server provisioning and environment deploys.

Git should be used for what it is build for.. versioning. And you do not want to version 3rd party packages (aka vendor folder) or anything else that is useless to version (like compiled files etc...)


@sg1asgard https://www.gitignore.io/ produces a lock file for Laravel with composer.lock ignored, FWIW.


I don't ignore my Vendor folder. Since I use Laravel Forge, it's nice to be able to push to a git repo then have Forge pull in the changes for me to update my website.


@kreierson Your composer.lock file already manage to keep the same version of packages you use in production.


I am seeing a lot of comments directing 'good idea' at using git for deployment, and checking in binaries and vendors... No one can stop you, but this is bad practice and will catch up with you, if not in the project, somewhere else. Really listen to advice for a bit.

vendors, ignored. That's why deployment tools do composer install for you, even heroku.

Please sign in or create an account to participate in this conversation.