Skip to content
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

Open
Filirom1 opened this issue Nov 21, 2012 · 2 comments
Open

Change git protocol in .git/config for the user #3

Filirom1 opened this issue Nov 21, 2012 · 2 comments

Comments

@Filirom1
Copy link
Member

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.

@sitepodmatt
Copy link
Member

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
Hostname localhost
Port 2222

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?

@Filirom1
Copy link
Member Author

I didn't know the .ssh/config global options. That's why I change the repo .git/config each time I do a openruko create.

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

git push heroku master become git push openruko master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants