netman.nvim VS sshfs

Hello Neovimers :) I posted this on the netman repo as well but I just wanted some opinions from users who use netman.

Lazy self promotion of netman.nvim which is designed to give you browse (and edit/read access) of remote systems without actually needing any configurations on said remote systems :)

I haven't been super active lately but Netman.nvim is my attempt to give neovim a solid remote editing experience. I've been taking a bit of time to myself though but it's still relatively stable for ssh and docker.

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

If there are any users of Netman already that also use windows (or users of Neovim that want to use Netman but can't because they are on a windows machine), please checkout the windows-compat branch!

Does that not write out to the current pty? That is an issue I have been facing with generic ssh support in netman. I have yet to come up with a decent solution to it :(

A quick bullet point list of features that are included in this point update - Mostly complete Neo-tree integration - Moving files and directories between hosts (including between docker containers and ssh servers) - Auto opening your remote "home" directory in ssh - A complete rewrite of how our "integration" with neovim works - A completely new logging system - A new event system

The password issue is currently something I am looking to address in netman though exploration into the area has proven unfruitful so far :/

Netman supports remote editing of files over ssh.

> 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.