sshfs VS sftp

> It's replaced sshfs for some cases.

I'd been using sshfs for some years until I learned that rclone can mount remotes to the file system, and I've been using that happily since then.

https://rclone.org/commands/rclone_mount/

> at present SSHFS does not have any active, regular contributors, and there are a number of known issues

https://github.com/libfuse/sshfs#development-status

Interesting, I alaways assumed sshfs was part of OpenSSH, learn something new every day.

Also, looks like sshfs used in Slackware is abandoned.

https://github.com/libfuse/sshfs

A quote from the link, I wonder if this project will be the 'one':

>If you would like to take over this project, you are welcome to do so. Please fork it and develop the fork for a while. Once there has been 6 months of reasonable activity, please contact [email protected] and I'll be happy to give you ownership of this repository or replace with a pointer to the fork.

I also wonder if it was abandoned due to the RHEL re-orgs like what happened to bluetooth.

SSHFS offers a solution for connecting to SSH servers through a network filesystem client. Enables users to seamlessly mount remote filesystems, without any server-side requirements. Underknowledge appreciates it "for mounting remote machines."

However, my setup relies on me using sshfs to "mount" a remote directory (which houses the media that jellyfin uses). For jellyfin to have access to this directory, it has to run the command under its user (based on sshfs manpages).

So I need to work with remote files and wondered how people here go about that. I've looked at sshfs, which seems the most obvious way to go and presumably would work fine (?), but it is an archived project; and tried distant.nvim, but that didn't click too well.

As far as I am aware, sshfs is no longer actively maintained.

After getting a bit discouraged since the easy solution failed, I ended up discovering that you can mount a remote filesystem over ssh using sshfs.

Determine the path inside the container where the data is. Its probably something like /home//upload Based on the image documentation here

If you use docker there is also a container for running sftp with custom users (different than the system users). You obviously need to use a different port, but you really should never expose SSH on port 22 anyway these days, if for no other reason than your logs will fill with bruteforce login attempts.