laravel command not found setting path does not work
up vote
9
down vote
favorite
I am have installed laravel via composer using the following procedure in my Ubuntu 17.04 running on the latest Oracle Virtualbox:
Steps:
1) composer global require "laravel/installer"
2) nano .bashrc
3) I added export PATH="$PATH:$HOME/.composer/vendor/bin"
4) saved changes.
I even added this line to .profile logged out then back in again but I am still getting laravel command not found.
What am I doing wrong?
laravel
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
asked Aug 8 '17 at 11:45
Nigel Smith
4614
add a comment |
up vote
9
down vote
favorite
I am have installed laravel via composer using the following procedure in my Ubuntu 17.04 running on the latest Oracle Virtualbox:
Steps:
1) composer global require "laravel/installer"
2) nano .bashrc
3) I added export PATH="$PATH:$HOME/.composer/vendor/bin"
4) saved changes.
I even added this line to .profile logged out then back in again but I am still getting laravel command not found.
What am I doing wrong?
laravel
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
asked Aug 8 '17 at 11:45
Nigel Smith
4614
do you found laravel binary on~/.composer/vendor/bin? maybe you set wrong path
– bhill77
Aug 8 '17 at 12:05
I think you might get this error because you are logged in asroot
– Thomas
Aug 8 '17 at 12:15
Did you reset apache?
– Taylor Foster
Aug 8 '17 at 12:39
1) The first suggestion isn't clear. 2) I logged in as a standard user 3) I rebooted the host PC but still the same error.
– Nigel Smith
Aug 8 '17 at 12:47
add a comment |
up vote
9
down vote
favorite
up vote
9
down vote
favorite
I am have installed laravel via composer using the following procedure in my Ubuntu 17.04 running on the latest Oracle Virtualbox:
Steps:
1) composer global require "laravel/installer"
2) nano .bashrc
3) I added export PATH="$PATH:$HOME/.composer/vendor/bin"
4) saved changes.
I even added this line to .profile logged out then back in again but I am still getting laravel command not found.
What am I doing wrong?
laravel
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
asked Aug 8 '17 at 11:45
Nigel Smith
4614
I am have installed laravel via composer using the following procedure in my Ubuntu 17.04 running on the latest Oracle Virtualbox:
Steps:
1) composer global require "laravel/installer"
2) nano .bashrc
3) I added export PATH="$PATH:$HOME/.composer/vendor/bin"
4) saved changes.
I even added this line to .profile logged out then back in again but I am still getting laravel command not found.
What am I doing wrong?
laravel
laravel
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
asked Aug 8 '17 at 11:45
Nigel Smith
4614
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
asked Aug 8 '17 at 11:45
Nigel Smith
4614
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
edited Aug 8 '17 at 15:17
Sujal Patel
1,2761926
1,2761926
asked Aug 8 '17 at 11:45
Nigel Smith
4614
asked Aug 8 '17 at 11:45
Nigel Smith
4614
asked Aug 8 '17 at 11:45
Nigel Smith
4614
4614
do you found laravel binary on~/.composer/vendor/bin? maybe you set wrong path
– bhill77
Aug 8 '17 at 12:05
I think you might get this error because you are logged in asroot
– Thomas
Aug 8 '17 at 12:15
Did you reset apache?
– Taylor Foster
Aug 8 '17 at 12:39
1) The first suggestion isn't clear. 2) I logged in as a standard user 3) I rebooted the host PC but still the same error.
– Nigel Smith
Aug 8 '17 at 12:47
add a comment |
do you found laravel binary on~/.composer/vendor/bin? maybe you set wrong path
– bhill77
Aug 8 '17 at 12:05
I think you might get this error because you are logged in asroot
– Thomas
Aug 8 '17 at 12:15
Did you reset apache?
– Taylor Foster
Aug 8 '17 at 12:39
1) The first suggestion isn't clear. 2) I logged in as a standard user 3) I rebooted the host PC but still the same error.
– Nigel Smith
Aug 8 '17 at 12:47
do you found laravel binary on
~/.composer/vendor/bin? maybe you set wrong path– bhill77
Aug 8 '17 at 12:05
do you found laravel binary on
~/.composer/vendor/bin? maybe you set wrong path– bhill77
Aug 8 '17 at 12:05
I think you might get this error because you are logged in as
root– Thomas
Aug 8 '17 at 12:15
I think you might get this error because you are logged in as
root– Thomas
Aug 8 '17 at 12:15
Did you reset apache?
– Taylor Foster
Aug 8 '17 at 12:39
Did you reset apache?
– Taylor Foster
Aug 8 '17 at 12:39
1) The first suggestion isn't clear. 2) I logged in as a standard user 3) I rebooted the host PC but still the same error.
– Nigel Smith
Aug 8 '17 at 12:47
1) The first suggestion isn't clear. 2) I logged in as a standard user 3) I rebooted the host PC but still the same error.
– Nigel Smith
Aug 8 '17 at 12:47
add a comment |
5 Answers
5
active
oldest
votes
up vote
7
down vote
For MAC users:
In terminal, type follow this:
1. nano ~/.bash_profile
2. export PATH="~/.composer/vendor/bin:$PATH"
If you are new in terminal, please try follow this youtube video.
answered Feb 28 at 9:31
Yuyang He
1,2242836
1
Thank you. It worked :)
– sadek
Apr 27 at 4:57
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
1
this worked for me
– Brainmaniac
May 6 at 9:46
add a comment |
up vote
2
down vote
You can save yourself the headache: install from composer:
composer create-project --prefer-dist laravel/laravel blog
blog is your project's name
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
Oh you use laravel 4.2? what error did you see runningcomposer create-project laravel/laravel your-project-name 4.2.*?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
add a comment |
up vote
1
down vote
Sometimes Laravel is not in that path. Instead try ~/.config/composer/vender/bin/. But make sure that laravel is exist in that path.
answered Aug 14 '17 at 3:16
dilantha111
306210
add a comment |
up vote
0
down vote
This is most likely because you haven't set the directory properly. I installed laravel as root so my directory was "/root/.composer/vendor/bin". Navigate to your home directory and do the following:
- vi .profile
- add /root/.composer/vendor/bin to the $PATH variable
- save file (:wq)
- source profile by typing: source .profile
-- remember, never install via root on a production server --
answered Feb 17 at 20:21
Lerie Taylor
13
1
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
add a comment |
up vote
0
down vote
I had the same problem with my Linux Mint. Check the composer folder path if this in ~/.config/composer then you need to change the $PATH variable looks like below.
This should solve the problem:
nano .bashrc [ or nano .bash_profile ]export PATH=~/.config/composer/vendor/bin:$PATH [ Add this line and save it ]source .bashrc
edited Nov 12 at 7:33
David Winder
3,0933725
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45567481%2flaravel-command-not-found-setting-path-does-not-work%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
For MAC users:
In terminal, type follow this:
1. nano ~/.bash_profile
2. export PATH="~/.composer/vendor/bin:$PATH"
If you are new in terminal, please try follow this youtube video.
answered Feb 28 at 9:31
Yuyang He
1,2242836
1
Thank you. It worked :)
– sadek
Apr 27 at 4:57
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
1
this worked for me
– Brainmaniac
May 6 at 9:46
add a comment |
up vote
7
down vote
For MAC users:
In terminal, type follow this:
1. nano ~/.bash_profile
2. export PATH="~/.composer/vendor/bin:$PATH"
If you are new in terminal, please try follow this youtube video.
answered Feb 28 at 9:31
Yuyang He
1,2242836
1
Thank you. It worked :)
– sadek
Apr 27 at 4:57
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
1
this worked for me
– Brainmaniac
May 6 at 9:46
add a comment |
up vote
7
down vote
up vote
7
down vote
For MAC users:
In terminal, type follow this:
1. nano ~/.bash_profile
2. export PATH="~/.composer/vendor/bin:$PATH"
If you are new in terminal, please try follow this youtube video.
answered Feb 28 at 9:31
Yuyang He
1,2242836
For MAC users:
In terminal, type follow this:
1. nano ~/.bash_profile
2. export PATH="~/.composer/vendor/bin:$PATH"
If you are new in terminal, please try follow this youtube video.
answered Feb 28 at 9:31
Yuyang He
1,2242836
answered Feb 28 at 9:31
Yuyang He
1,2242836
answered Feb 28 at 9:31
Yuyang He
1,2242836
answered Feb 28 at 9:31
Yuyang He
1,2242836
1,2242836
1
Thank you. It worked :)
– sadek
Apr 27 at 4:57
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
1
this worked for me
– Brainmaniac
May 6 at 9:46
add a comment |
1
Thank you. It worked :)
– sadek
Apr 27 at 4:57
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
1
this worked for me
– Brainmaniac
May 6 at 9:46
1
1
Thank you. It worked :)
– sadek
Apr 27 at 4:57
Thank you. It worked :)
– sadek
Apr 27 at 4:57
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
@sadek my pleasure :)
– Yuyang He
Apr 27 at 6:17
1
1
this worked for me
– Brainmaniac
May 6 at 9:46
this worked for me
– Brainmaniac
May 6 at 9:46
add a comment |
up vote
2
down vote
You can save yourself the headache: install from composer:
composer create-project --prefer-dist laravel/laravel blog
blog is your project's name
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
Oh you use laravel 4.2? what error did you see runningcomposer create-project laravel/laravel your-project-name 4.2.*?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
add a comment |
up vote
2
down vote
You can save yourself the headache: install from composer:
composer create-project --prefer-dist laravel/laravel blog
blog is your project's name
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
Oh you use laravel 4.2? what error did you see runningcomposer create-project laravel/laravel your-project-name 4.2.*?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
add a comment |
up vote
2
down vote
up vote
2
down vote
You can save yourself the headache: install from composer:
composer create-project --prefer-dist laravel/laravel blog
blog is your project's name
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
You can save yourself the headache: install from composer:
composer create-project --prefer-dist laravel/laravel blog
blog is your project's name
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
answered Aug 8 '17 at 12:50
Oluwatobi Samuel Omisakin
3,07111029
3,07111029
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
Oh you use laravel 4.2? what error did you see runningcomposer create-project laravel/laravel your-project-name 4.2.*?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
add a comment |
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
Oh you use laravel 4.2? what error did you see runningcomposer create-project laravel/laravel your-project-name 4.2.*?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
I followed these instructions to the letter but still no joy laravel.com/docs/4.2/quick.
– Nigel Smith
Aug 8 '17 at 13:31
Oh you use laravel 4.2? what error did you see running
composer create-project laravel/laravel your-project-name 4.2.*?– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
Oh you use laravel 4.2? what error did you see running
composer create-project laravel/laravel your-project-name 4.2.*?– Oluwatobi Samuel Omisakin
Aug 8 '17 at 14:10
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I saw the error I made, so I followed the instructions given in laravel.com/docs/5.4, but I am still getting a laravel command not found. Very frustrating!
– Nigel Smith
Aug 8 '17 at 15:50
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
I mean don't use laravel command. use composer to install laravel package. can you add (the full error you get to your question) after running the command i gave in my answer?
– Oluwatobi Samuel Omisakin
Aug 8 '17 at 18:04
add a comment |
up vote
1
down vote
Sometimes Laravel is not in that path. Instead try ~/.config/composer/vender/bin/. But make sure that laravel is exist in that path.
answered Aug 14 '17 at 3:16
dilantha111
306210
add a comment |
up vote
1
down vote
Sometimes Laravel is not in that path. Instead try ~/.config/composer/vender/bin/. But make sure that laravel is exist in that path.
answered Aug 14 '17 at 3:16
dilantha111
306210
add a comment |
up vote
1
down vote
up vote
1
down vote
Sometimes Laravel is not in that path. Instead try ~/.config/composer/vender/bin/. But make sure that laravel is exist in that path.
answered Aug 14 '17 at 3:16
dilantha111
306210
Sometimes Laravel is not in that path. Instead try ~/.config/composer/vender/bin/. But make sure that laravel is exist in that path.
answered Aug 14 '17 at 3:16
dilantha111
306210
answered Aug 14 '17 at 3:16
dilantha111
306210
answered Aug 14 '17 at 3:16
dilantha111
306210
answered Aug 14 '17 at 3:16
dilantha111
306210
306210
add a comment |
add a comment |
up vote
0
down vote
This is most likely because you haven't set the directory properly. I installed laravel as root so my directory was "/root/.composer/vendor/bin". Navigate to your home directory and do the following:
- vi .profile
- add /root/.composer/vendor/bin to the $PATH variable
- save file (:wq)
- source profile by typing: source .profile
-- remember, never install via root on a production server --
answered Feb 17 at 20:21
Lerie Taylor
13
1
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
add a comment |
up vote
0
down vote
This is most likely because you haven't set the directory properly. I installed laravel as root so my directory was "/root/.composer/vendor/bin". Navigate to your home directory and do the following:
- vi .profile
- add /root/.composer/vendor/bin to the $PATH variable
- save file (:wq)
- source profile by typing: source .profile
-- remember, never install via root on a production server --
answered Feb 17 at 20:21
Lerie Taylor
13
1
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
add a comment |
up vote
0
down vote
up vote
0
down vote
This is most likely because you haven't set the directory properly. I installed laravel as root so my directory was "/root/.composer/vendor/bin". Navigate to your home directory and do the following:
- vi .profile
- add /root/.composer/vendor/bin to the $PATH variable
- save file (:wq)
- source profile by typing: source .profile
-- remember, never install via root on a production server --
answered Feb 17 at 20:21
Lerie Taylor
13
This is most likely because you haven't set the directory properly. I installed laravel as root so my directory was "/root/.composer/vendor/bin". Navigate to your home directory and do the following:
- vi .profile
- add /root/.composer/vendor/bin to the $PATH variable
- save file (:wq)
- source profile by typing: source .profile
-- remember, never install via root on a production server --
answered Feb 17 at 20:21
Lerie Taylor
13
edited Feb 17 at 21:02
answered Feb 17 at 20:21
Lerie Taylor
13
answered Feb 17 at 20:21
Lerie Taylor
13
answered Feb 17 at 20:21
Lerie Taylor
13
13
1
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
add a comment |
1
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
1
1
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
Don't do everything as root, and don't encourage that. Bad behavior because it breaks the user permission model.
– sorak
Feb 17 at 20:53
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
I've modified my post to let people know not to do it as root but nowhere in my answer did I tell anyone to "do everything as root" or encourage it, but thanks for your concern.
– Lerie Taylor
Feb 18 at 4:05
add a comment |
up vote
0
down vote
I had the same problem with my Linux Mint. Check the composer folder path if this in ~/.config/composer then you need to change the $PATH variable looks like below.
This should solve the problem:
nano .bashrc [ or nano .bash_profile ]export PATH=~/.config/composer/vendor/bin:$PATH [ Add this line and save it ]source .bashrc
edited Nov 12 at 7:33
David Winder
3,0933725
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
add a comment |
up vote
0
down vote
I had the same problem with my Linux Mint. Check the composer folder path if this in ~/.config/composer then you need to change the $PATH variable looks like below.
This should solve the problem:
nano .bashrc [ or nano .bash_profile ]export PATH=~/.config/composer/vendor/bin:$PATH [ Add this line and save it ]source .bashrc
edited Nov 12 at 7:33
David Winder
3,0933725
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the same problem with my Linux Mint. Check the composer folder path if this in ~/.config/composer then you need to change the $PATH variable looks like below.
This should solve the problem:
nano .bashrc [ or nano .bash_profile ]export PATH=~/.config/composer/vendor/bin:$PATH [ Add this line and save it ]source .bashrc
edited Nov 12 at 7:33
David Winder
3,0933725
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
I had the same problem with my Linux Mint. Check the composer folder path if this in ~/.config/composer then you need to change the $PATH variable looks like below.
This should solve the problem:
nano .bashrc [ or nano .bash_profile ]export PATH=~/.config/composer/vendor/bin:$PATH [ Add this line and save it ]source .bashrc
edited Nov 12 at 7:33
David Winder
3,0933725
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
edited Nov 12 at 7:33
David Winder
3,0933725
edited Nov 12 at 7:33
David Winder
3,0933725
edited Nov 12 at 7:33
David Winder
3,0933725
3,0933725
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
answered Nov 12 at 5:14
Shashi Asanka Nawarathna
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45567481%2flaravel-command-not-found-setting-path-does-not-work%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
do you found laravel binary on
~/.composer/vendor/bin? maybe you set wrong path– bhill77
Aug 8 '17 at 12:05
I think you might get this error because you are logged in as
root– Thomas
Aug 8 '17 at 12:15
Did you reset apache?
– Taylor Foster
Aug 8 '17 at 12:39
1) The first suggestion isn't clear. 2) I logged in as a standard user 3) I rebooted the host PC but still the same error.
– Nigel Smith
Aug 8 '17 at 12:47