-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change git protocol in .git/config for the user #3
Comments
I initially left it as git@whatever because thats what Heroku toolbelt uses, also implicitly git will use ssh as its transport unless a explicit directive exists. To change this you would have fork toolbelt which I dont think is necessary. In testing enviornment one can specify port by: In my .ssh/config I have Host testopenruko In production or 3rd party hosted environments I presume most people leave the default port in which case justhostname works. Im flexible though if you want to persist this way, is it possible without changing Heroku toolbelt? |
I didn't know the Instead of launching a bash hat, we can launch a node hat, that do some replacement in the stdout and stderr of the officiel heroku. For exemple s/heroku/openruko/g
|
Curently in the README there is an important note, if user want to use OpenRuko.
CHANGE heroku remote to use the ssh protocol insted of the git protocol, replace [email protected] to ssh:https://openruko.com:2222 in your .git/config
It would be great to not ask the user to change the .git/config, and do it automatically.
The text was updated successfully, but these errors were encountered: