edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: ftp scp uploads
Date: Mon, 11 Jul 2022 01:11:18 -0400	[thread overview]
Message-ID: <20220611011118.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

Dave gave me something interesting to work on, (thank you), and so I did.
ftp and scp uploads.
But I have only been able to test scp, I don't have a writeable ftp server handy, so can't guarantee that one.
But scp is pretty cool. Give it a try.

e scp://login:password@whatever.com/home/mylogin/some_file
make some changes

It all works, but, as I mentioned on the chat group,
1. I can't use keys to ssh in; I have to specify login and password, which is kind of a pain. Is that a limitation of curl, or is there some other way to tell it to use public keys? Some sites only allow for ssh with keys.
2. I have to specify the absolute path, it starts from / not from my home directory. This is different I think from how ftp works. Also different from the shell scp command, so is confusing.

I haven't documented these in detail, not sure how they work yet, or even if ftp works at all.
I did add them to the quick list of commands, that you see by typing help.

The downloads, like all downloads, can happen in the background, if bg is set,
but uploads are always in foreground.
I think this is reasonable, you're more likely to ftp down a huge file, than to ftp up.

Karl Dahlke

             reply	other threads:[~2022-07-11  5:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  5:11 Karl Dahlke [this message]
2022-07-11  6:18 ` Dominique Martinet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220611011118.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=edbrowse-dev@edbrowse.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).