3 ms·
> giving you more control over your instances and the ability to SSH into them. FWIW you can do: heroku run bash Which let's you mess around on a new dyn
by pearkes 13y ago
> giving you more control over your instances and the ability to SSH into them.
FWIW you can do:
heroku run bash
Which let's you mess around on a new dyno (not an existing one).
- edanm 13y agoDidn't know about this. What's the difference between a new dyno and an existing one? Why would they act differently?
- ncrit 13y agoThey don't act differently, its just a dyno separate from the web and other processes.
- vishal0123 13y agoThe changes you made by running 'heroku run bash' is temporary and can be reverted any time.
- acjohnson55 13y agoThat's good for things that change shared state, but you can't do anything that would alter a running dyno or interrogate its state, unless you built your own hooks or something. But building something like that would kind of obviate the perks of a NoOps system.
- fabiokung 13y ago`heroku run bash` is still the best option, but I've always wanted to ssh into heroku dynos myself, so I did this: https://github.com/fabiokung/heroku-ssh https://github.com/fabiokung/heroku-ssh