netman.nvim VS nvim-docker

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.

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.