heroku_san
heroku_san copied to clipboard
Console not starting.
$ heroku version
heroku-toolbelt/3.43.9 (x86_64-darwin15) ruby/2.3.1
heroku-cli/5.2.39-010a227 (darwin-amd64) go1.6.2
You have no installed plugins.
$ gem list heroku_san
*** LOCAL GEMS ***
heroku_san (4.4.0)
heroku_san wants to start the console like so:
heroku run console --app <my-app> --exit-code
However, this produces the following response:
Running console on ⬢ <my-app>... up, run.1663
bash: console: command not found
▸ Process exited with code 127
Removing --exit-code causes the Toolbelt command to work.
hmmm, it should be "rails console", not just console. Which "rake" command were you running that caused this error?
On Wed, Aug 24, 2016 at 10:54 AM, Jon Frisby [email protected] wrote:
$ heroku version heroku-toolbelt/3.43.9 (x86_64-darwin15) ruby/2.3.1 heroku-cli/5.2.39-010a227 (darwin-amd64) go1.6.2 You have no installed plugins.
$ gem list heroku_san
*** LOCAL GEMS ***
heroku_san (4.4.0)
heroku_san wants to start the console like so:
heroku run console --app
--exit-code However, this produces the following response:
Running console on ⬢ verydice-production... up, run.1663 bash: console: command not found ▸ Process exited with code 127
Removing --exit-code causes the Toolbelt command to work.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jqr/heroku_san/issues/176, or mute the thread https://github.com/notifications/unsubscribe-auth/AABM5A8dipKznXxkh_FQ5psO-jJeQnizks5qjIVtgaJpZM4JsRxD .
CTO, PacerPro, Inc. https://www.pacerpro.com Want to talk to me? Schedule an appointment here: https://calendly.com/ken-pacerpro/15min
rake staging console