nvim-docker VS distant.nvim

Theres quite a few options, most notably I prefer to use https://github.com/dgrbrady/nvim-docker for interacting with containers, along with https://github.com/miversen33/netman.nvim/tree/issue-28-libuv-shenanigans for remote development

I don't remember where I got this code from, but in the plug-in i'm working on, I have the ,w binding set to reload the package. That way, when I make a change I just use that keybinding to reload my changes instead of closing and reopening neovim. Here's the file that sets that up: https://github.com/dgrbrady/nvim-docker/blob/main/dev/init.lua Replace the package name on line 4 and the function call on line 24 with your specific code, then execute :luafile dev/init.lua to load that file to enable the keybinding. you only have to do this once

For example container-layout returns a ContainerLayout whereas container-logs returns _M, and docker return docker

So I spent the past few days writing my first ever Neovim Lua plugin, nvim-docker. It's really early in development and only supports viewing containers on your machine with live reloading of your containers statuses. I have tons of features I'd love to implement, but wanted to get some feedback from the community on the project.

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.