distant.nvim VS sshfs

Oops, meant distant, https://distant.dev/.

2) There is a remote working plugin to not have the overhead of sshfs copying around files https://github.com/chipsenkbeil/distant.nvim, but you could also role your own with neovim now having remote mode and lua runner. Main caveat is how to get consistent file system view.

- What do you think of other plugins e.g.: https://github.com/chipsenkbeil/distant.nvim?

This is something I've been tracking pretty closely. My understanding of the current options: 1. Use sshfs. Pros: nothing to install on the remote server. Cons: will choke on huge filesystems when doing some operations (e.g. fuzzy finding). Also requires all your LSP/linting/analysis tools to be installed locally, which may not be the case if your company is transitioning to remote developer environments. 2. Use netrw or similar. Pros: nothing to install. Cons: will not play nice with LSP, fuzzy finding, or anything else. 3. Use distant.nvim. At this point, basically the same as netrw except that maybe remote LSP will work. 4. SSH to the server and use nvim there. Pros: simple and everything works. Cons: Have to install nvim on the server. SSH connection may cause typing lag if the RTT is high (some people report that Mosh can help the lag issue)

The reason being is that I've written a service called distant with a companion neovim plugin, distant.nvim, and want to provide forms of authentication in the same vein as ssh.

Did a lot if research. there is distant.nvim that tries to solve it maybe it will work for you.

I either use the vi / vim that's on the server or connect remotely using https://github.com/chipsenkbeil/distant.nvim

Regarding the last part of your comment: you may get some value out of this plugin, https://github.com/chipsenkbeil/distant.nvim, https://www.youtube.com/watch?v=wVAsbpByQ3o.

I've not used it but your use case made me wonder if there's a nice way to do it, as I regularly SSH into my NAS and RPi's, so I had a quick search.

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