laravel/.gitignore

/node_modules
/public/storage
/public/hot
/storage/*.key
/vendor
/.idea
/.vagrant
Homestead.json
Homestead.yaml
.env
Add "node_modules" to .gitignore Seems sensible if Laravel's going to push Elixir. A person unfamiliar with the node ecosystem should be able to use Elixir with ease, however I don't feel they should necessarily know up-front that they should add node_modules to their global .gitignore file. 2015-02-01 11:16:11 +00:00			`/node_modules`
add to gitignore 2016-02-12 09:05:19 -06:00			`/public/storage`
Remove the hot file from versionning Following https://github.com/laravel/framework/pull/17571, I was correctly pointed that the small proposition should be made over here. Here's a copy / past of my message, for clarity's sake. --- When you run `npm run hmr`, a `hot` file is created to the public folder for the `mix()` helper to know if it has to server from the webpack server or not. This file does not go away until we run `npm run dev` (or `watch`). True, if we use `npm run production` in our production server it goes away too, but in case we don't make it go away in development, I don't think it's necessary to version it. 2017-01-26 21:22:52 -05:00			`/public/hot`
Ignore Passport-generated OAuth keys These files should not end up in source control IMO. And even though Passport is a separate package it is a first-party one and the base Laravel install should be "prepared" for it. What do you guys think? 2016-10-12 15:51:50 +03:00			`/storage/*.key`
Fix order Fix .gitignore items in alphabetical order. 2016-08-22 17:02:27 +07:00			`/vendor`
Fix order 2016-08-13 18:42:51 -07:00			`/.idea`
Add vagrant virtual machine directory to git ignore list. 2017-03-28 09:36:45 +01:00			`/.vagrant`
Ignore Homestead.json 2015-07-25 12:57:52 -07:00			`Homestead.json`
Fix order Fix .gitignore items in alphabetical order. 2016-08-22 17:02:27 +07:00			`Homestead.yaml`
Simplify environment loading. 2014-10-08 17:12:10 -05:00			`.env`