nvim-dev-container VS distant.nvim

As you can see from the customizations section, Dev Containers are IDE agnostic. For example, there is a project implementing Dev Container support into nvim. But since the Visual Studio Code (vscode) team at Microsoft invented Dev Containers, it is currently the IDE with the best Dev Container experience.

Is there any extension that fullty supports the dev.json spec? I tried this : https://github.com/esensar/nvim-dev-container But it looks like it doesn`t add any of the features I set on the dev.json. I also cant seem to make the :terminal command attach to the container - it does work on VsCode :z.

How do you achieve the devcontainer experience without any VS Code? I am aware of plugins like https://github.com/jamestthompson3/nvim-remote-containers and https://github.com/esensar/nvim-dev-container however I didn't figure them out and they don't seem very active.

esensar/nvim-dev-container

nvim-dev-container provides functionality related to devcontainer.json file, similar to VSCods's remote container development.

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.