Geek Answers Handbook

What are the main differences between composer create-project and git clone?

I would like to develop a Laravel-based web application without contributing to the framework. I like to get updates from the framework periodically when developing my own web application. I would also like to use the version control system for myself and my teammate.

I'm not sure which strategy to use between

Using composer

composer create-project laravel/laravel webproject --prefer-dist

And periodically keep updating with Laravel using

composer update

Using git

git clone https://github.com/laravel/laravel.git webproject

And periodically keep updating with Laravel using

git pull

What are the main differences between the two? One of them is that the composer create-project -perfer-dist comes with cleared version control, what else?

If I used to use the git clone to get an update from the framework using the composer update, can it hurt?

+4
1

, , , , . .

, , , , . , , , - , , .

, , - , , , .

, - , - .

: composer update composer.json, . Laravel, 4.0. *. git pull , , ( - ), Laravel, . composer update.

, , . , Composer , .

+3

More articles:


All Articles