devc
cli tool to manage your devcontainers (by nikaro)
nvim-docker
By dgrbrady
devc | nvim-docker | |
---|---|---|
1 | 5 | |
50 | 119 | |
- | - | |
10.0 | 0.0 | |
11 months ago | 4 months ago | |
Go | Lua | |
GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
devc
Posts with mentions or reviews of devc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-13.
-
Neovim + Docker?
If you are talking about "remote container" i wrote this tool to do exactly that: https://github.com/nikaro/devc
nvim-docker
Posts with mentions or reviews of nvim-docker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-13.
-
Neovim + Docker?
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
-
What's the best practice for developing neovim plugins in Lua?
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
-
Huge nvim-docker updates!!
For example container-layout returns a ContainerLayout whereas container-logs returns _M, and docker return docker
-
Introducing nvim-docker, The Missing Docker Management Lua Plugin
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.
What are some alternatives?
When comparing devc and nvim-docker you can also consider the following projects:
nvim-dev-container - Neovim dev container support - Mirror of https://codeberg.org/esensar/nvim-dev-container
netman.nvim - Neovim (Lua powered) Network Resource Manager
lazydocker - The lazier way to manage everything docker
vim-kubernetes - vim-kubernetes
nvim-remote-containers - Develop inside docker containers, just like VSCode