foreman: command not found

Question

I am following this tutorial of Heroku. I installed foreman with

sudo gem install foreman

but when I try to use this in the terminal with command

foreman

this returns

foreman: command not found

score 7 · Answer 1 · answered Oct 07 '11 at 20:44

7

Just got the same error: foreman command not found.
I managed to succeed removing my gem with:

sudo gem uninstall foreman

And re-install it back with rvm.

rvm gem install foreman

Good luck!

answered Oct 07 '11 at 20:44

ASX

171

5

This gave me the clue for getting it to work with rbenv: gem install foreman; rbenv rehash – B Seven Sep 21 '12 at 18:19
Please note that rvm gem ... was removed, try gem install foreman or rvm all do gem install foreman instead. – Tarun Kolla Nov 04 '19 at 22:14

score 6 · Accepted Answer · answered Sep 14 '11 at 00:02

6

I would check where gem installs executables into and add that directory to your PATH.

answered Sep 14 '11 at 00:02

score 4 · Answer 3 · answered Nov 21 '11 at 05:54

gem install foreman

was all I needed to do

However, when I followed the deb instructions on this page: http://theforeman.org/projects/foreman/wiki/Installation_instructions I had lots of issues...Eventually, I completely uninstalled before running gem install foreman. Then it worked like a charm.

score 0 · Answer 4 · answered Nov 30 '22 at 22:24

0

I agree with the accepted answer that the issue might be with PATH.

If you run rbenv put this to your ~/.bashrc or ~/.bash_profile:

export PATH="$PATH:~/.rbenv/shims”

Then source the file and check for foreman: which foreman.

answered Nov 30 '22 at 22:24

Evgeny Mikhaylov

129
1
10

score 0 · Answer 5 · answered Sep 14 '11 at 00:02

You haven't given quite enough information for the problem to be properly diagnosed. (Eg, give a link to the tutorial, indicate if you tested foreman by itself, and tell us what "this" is, ie what command you entered or selected.)

If the install appeared to be ok, and if which foreman reports a reasonable path to foreman, and if the invocation that failed is in a non-interactive shell, then the usual problem is a different $PATH value in that shell, and the usual solution is to specify a fully-qualified path.

foreman: command not found

5 Answers5