Laravel Framework - Difference between creating a new project via laravel or composer?

Question

Been following along several Laravel tutorials online and they all create a new project through either of these two commands:

laravel new project-name

or

composer create-project laravel/laravel project-name

They both seem to generate the same template, but are there any differences between the two one should know about? Laravel docs are unclear on this, and couldn't find an answer online, would appreciate if someone can clear it up for me.

You can check yourself by doing a recursive diff on the two directories. There should be no difference AFAIK. The source code for laravel new project-name is at github.com/laravel/installer/blob/master/src/NewCommand.php — Ben Claar
– Ben Claar, Commented Aug 8, 2015 at 2:52

Andrew Hood · Accepted Answer · 2015-08-08 05:30:57Z

9

composer create-project laravel/laravel project-name will do two extra things as far as I know. These are executed because of scripts in composer.json

cp .env.example .env
./artisan key:generate

composer.json

answered Aug 8, 2015 at 5:30

Andrew Hood

1584 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Leonardo Sibela Over a year ago

Andrew Hood, could you explain a little better what the #2 thing is?

Jideobi Benedine Ofomah Over a year ago

@LeonardoSibela #2 generates application secret key and assigns it to app key field in your .env file created in step #1.

Collectives™ on Stack Overflow

Laravel Framework - Difference between creating a new project via laravel or composer?

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related