composer create-project laravel/laravel returns permission denied

MBP is a Mac ? Maybe this helps.

@bestmomo Unfortunately, it doesn't work :/

OK. I had to open a folder which will then belong to me and then run the command:

sudo chmod 777 code

After doing that I can use composer as intended inside the code directory.

open a folder which will then belong to me ... sudo chmod 777 code

You changed the permissions of this folder not ownership. Error is most likely Composer permissions issue. It's being denied write permissions. How did you install Composer?

This is not the way to go about it. Neither is it good to show that as a solution, it's a bad security risk and practice.

alenabdula, How do we correct the install of Composer so it is not denied write permissions?

@dhorowitz1 Well, first check the current permissions

ls -lah `which composer`

Then you can do something like

sudo chmod a+x `which composer`

http://stackoverflow.com/questions/18596778/difference-between-using-chmod-ax-and-chmod-755

@bashy Sorry, I might be a little slow at this, I'm pretty new. When you say 'which composer', what does that mean?

That's what you'd type exactly. If you do man which (man = manual).

man which

NAME
     which -- locate a program file in the user's path

Running it within ` just executes that command then outputs the result so it's like an automatic way of getting a dynamic path. Can be different on other people's computer but this one command will work for all (so to speak).