There is a project on Laravel. How to correctly upload its files to the Git repository?

Question

git

There is a project on Laravel. How to correctly upload its files to the Git repository? Do I need to keep track of all files? Which files should be ignored and which should not?

Answer 1

https://github.com/laravel/laravel/blob/master/.gi...
Laravel already has a gitignor, if you delete it, then return it to its place, and quietly commit yourself.

Answer 2

I would suggest that you don't commit Laravel to git .
I guess the story started like this: you download the Laravel source code from git. Later, edit the app immediately, add controllers. Then from the same folder think of a web server and see the result.
I suggest you organize three folders:
- A folder with the Laravel source code. Slope with the git. And git pull from time to time. (this is in case Laravel cannot be registered in the project composer.json)
- Folder with your project. It has its own .gitignore, no caches, no rubbish in the face of the app engine.
- And a magical third folder. The web server looks into it. Files from the first two are merged into it. This folder organically appears if the web server is set up on a local virtual machine, or on a remote server.
A convenient connection of several folders to the project can be done in PhpStorm and NetBeans (it seems). Well, auto-deploy by Cmd+S.