Confirmed users
67
edits
ReleaseEngineering/How To/Heroku CLI: Difference between revisions
ReleaseEngineering/How To/Heroku CLI (view source)
Revision as of 06:51, 13 June 2019
, 13 June 2019minor edits
(How to work with Heroku CLI) |
m (minor edits) |
||
| Line 3: | Line 3: | ||
# Go to: https://mozillians.org and login your Mozilla LDAP account. | # Go to: https://mozillians.org and login your Mozilla LDAP account. | ||
# Go to: https://mozillians.org/en-US/group/heroku-members/ and click Request Access. | # Go to: https://mozillians.org/en-US/group/heroku-members/ and click Request Access. | ||
# | # Wait for the request to join the group to be approved. Usually takes a day or less. | ||
# DO THE NEXT STEPS ONLY AFTER YOU ARE APPROVED! | # DO THE NEXT STEPS ONLY AFTER YOU ARE APPROVED! | ||
# Activate SSO via this [https://sso.heroku.com/saml/mozillacorporation/init HEROKU Link] | # Activate SSO via this [https://sso.heroku.com/saml/mozillacorporation/init HEROKU Link] | ||
# Bookmark [https://sso.heroku.com/saml/mozillacorporation/init THIS LINK]. Once you activate SSO, you won't be able to login using the normal login page! So make sure the bookmark is in place! | # Bookmark [https://sso.heroku.com/saml/mozillacorporation/init THIS LINK]. Once you activate SSO, you won't be able to login using the normal login page! So make sure the bookmark is in place! | ||
# Install Heroku for | # Install Heroku for your OS. | ||
# Open | # Open your favorite terminal and type '''heroku login'''. The page should tell you that you can safely logout and the terminal should tell you that you have logged in on your account. | ||
# When you are done with the previous steps, login on heroku and see if you are member of 'mozillacorporation' team. | # When you are done with the previous steps, login on heroku's website/dashboard and see if you are member of 'mozillacorporation' team. | ||
== Heroku CLI commands == | == Heroku CLI commands == | ||
| Line 21: | Line 21: | ||
heroku dyno:restart --app <heroku-service-name> | heroku dyno:restart --app <heroku-service-name> | ||
Between dyno:restart and --app, you can add a specific dyno name which will restart only the selected dyno: | Between dyno:restart and --app, you can add a specific dyno name which will restart only the selected dyno: | ||
heroku dyno:restart <dyno> --app <heroku-service-name> | heroku dyno:restart <dyno-name> --app <heroku-service-name> | ||
== When do we restart the dynos (processes)? == | == When do we restart the dynos (processes)? == | ||
| Line 27: | Line 27: | ||
It is okay, and recommended, to restart all dynos (eg don't provide a name between dyno:restart and --app). | It is okay, and recommended, to restart all dynos (eg don't provide a name between dyno:restart and --app). | ||
If you need to restart more services, lets say 3 of them, there is no order that the restart needs to follow. Simply reboot them, all should go smooth | If you need to restart more services, lets say 3 of them, there is no order that the restart needs to follow. Simply reboot them, all should go smooth. | ||
How do you know that a services is responsible for a problem? | How do you know that a services is responsible for a problem? | ||