Heroku deprecates SSH Git transport
devcenter.heroku.com
devcenter.heroku.com
> Heroku will retire the SSH transport feature and all git pushes must be done using the more widely used HTTP Git transport.
How can HTTP be more widely used by SSH? Is this really true? Is it because Heroku encourage it in their setup documentation?
I'm seeing this trend elsewhere, such as GitHub [1]. Why are services that support Git trying to encourage users not to use SSH?
[1]: https://docs.github.com/en/get-started/quickstart/set-up-git...
- It is easiest to set up on the widest range of networks and platforms and is easier for people to get started in a simple and secure way.
- It does not require to generate/copy/paste ssh keys in the git server provider.
- It is easier to access and write on repositories from anywhere and you just need account details.
- HTTPS is a port that is open in all firewalls and does not require to open by doing to firewall settings.
So based on that I can see why they would prefer to push https as it’s easier/more interoperable and therefore a better default for “most” people.
However, personally I prefer using the SSH protocol. I don’t get why they would deprecate it though..
But this is all from the perspective of a user choosing one over the other and doesn't discuss why a service would encourage one over the other. What I'm expecting is "HTTPS is faster / easier to load-balance / etc.", but I really don't know.