I develop locally on Laravel, periodically pushing into a remote repository. Have questions:

  1. What would you advise to write to the file README.MD (now there is a description of the Laravel framework)? Brief description of the project or full documentation?

  2. Inside the Laravel distribution there is a .gitignore file, among other things, it contains the vendor folder, i.e. it does not get to the remote repository. I work according to this scheme: I develop it locally, push it into the remote, then from there I take it to dev.myproject.com and show it to the boss. When I take away, the vendor folder, of course, no, I have to upload it there separately, in the old fashioned way, by ftp. It confuses me, everyone does that?

    1 answer 1

    1) README.md should briefly describe the project and how to "deploy" it. It is also a good idea to point out the linking and linking libraries used.

    2) Usually the vendor folder does not change handles. Therefore, it is not necessary to push it into the repository. And for management is used composer. It is his task to download and configure everything. And what would be all good and easy on the market, usually build scripts are made. And you can configure these scripts to trigger on git push in master. As a result, everything will automatically turn around.

    • Thank. I have a site on a virtual hosting, there is only git, there is no composer, and there are no scripts to run there. - pavelchervov
    • if git is there and you can run it, then most likely you have access to the console (for example, via http). So, you can run scripts on a bash or on the same php. In the extreme case, you can make yourself a script, then the stream will be launched from the browser later - it is already difficult to prevent it. Somewhere the installation works popular joomla, drupal and the like. - KoVadim