Remove SCP references in Fabric doc

[omzev]

I was looking for a way to use SCP via Fabric, and after some investigation found issue #945 (Allow option for get/put to be handled by scp), currently closed.

See Paramiko #150 - Fabric won't be able to take any action on this until we decide how/whether Paramiko should.

Originally posted by @bitprophet in #945 (comment)

That was in 2013, and the question still seems open regarding how to do SCP instead of SFTP.

fabric/fabric/transfer.py

Line 26 in e9939d6

# TODO: SFTP clear default, but how to do SCP? subclass? init kwarg?

Given that Fabric cannot use SCP for transfers, can the documentation be updated to reflect that by omitting SCP? Might save others some investigative effort.

Thanks for your time!

PS: I'm still using Fabric for SSH workflows. Very easy to use! 👍

[karlcow]

I addressed this in #2029

[anarcat]

scp seems less and less recommended by SSH upstream anyways, so it makes sense to remove it.

[bojanpotocnik]

My SSH host does not support SFTP, only SCP and reading

File transfer via SFTP and/or SCP.

made it obvious to me that I can somehow select which protocol do I wish to use. And yes, afer some time searching trough the sources and then on the internet, I am here with exactly the same question.

[jarhainx]

+1
My client doesn't support sftp and I wasted time believing it was possible because the doc is wrong.

Can you remove the scp mention from the documentation or mention that this is not possible?
Thank you

[magnificantsugarglider]

+1
My client also doesn't support SFTP protocol and I also wasted long hours of forcing fabric made file transfer. Please, change the documentation.

[anarcat]

can we limit the number of +1 comments here? you can simply hit the 👍 button on the original comment instead, instead of ringing everyone here.

[LOGUNIVPM]

Hi, I still see the misleading mention to SCP in https://docs.fabfile.org/en/stable/api/transfer.html
Is that a leftover?