features
nvim-dev-container
Our great sponsors
features | nvim-dev-container | |
---|---|---|
7 | 7 | |
749 | 493 | |
7.2% | - | |
9.0 | 7.9 | |
about 23 hours ago | 4 days ago | |
Shell | Lua | |
MIT License | MIT License |
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.
features
-
Dev Containers: Open, Develop, Repeat...
Dev Containers not only allow you to define which extensions should be installed and which configuration settings shall be set, but they also have something they call "Dev Container Features".
-
Unable to Change Workspace Folder Permissions (777 to 775) in WSL VSCode Devcontainer
json { "name": "Ubuntu", // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile "image": "mcr.microsoft.com/devcontainers/base:ubuntu", "features": { "ghcr.io/devcontainers/features/terraform": "latest", "ghcr.io/devcontainers/features/powershell": "latest", "ghcr.io/devcontainers/features/azure-cli": "latest" }, // Features to add to the dev container. More info: https://containers.dev/features. // "features": {}, // Use 'forwardPorts' to make a list of ports inside the container available locally. // "forwardPorts": [], // Use 'postCreateCommand' to run commands after the container is created. // "postStartCommand": "uname -a", // "postCreateCommand": "sudo apt update; sudo apt upgrade -y;", "postAttachCommand": { "git-safe-directory": "git config --global --add safe.directory ${containerWorkspaceFolder}", "ansible_cfg_permissions": "sudo chmod o-w ${containerWorkspaceFolder}" }, "postCreateCommand": { "python": "sudo apt update; sudo apt upgrade -y; sudo apt install -y python3-pip postgresql-client; sudo python3 -m pip install --upgrade pip; pip3 install ansible python-hcl2 psycopg2-binary; ansible-galaxy collection install azure.azcollection", "populate-history": "echo 'ansible-playbook ansible/playbooks/netbox.yml' >> ~/.bash_history; echo 'terraform apply' >> ~/.bash_history; echo 'az login' >> ~/.bash_history" }, // Configure tool-specific properties. // "customizations": {}, // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. // "remoteUser": "root" "customizations": { "vscode": { "extensions": [ "GitHub.copilot", "GitHub.copilot-labs", "GitHub.vscode-pull-request-github", "redhat.ansible", "hashicorp.terraform", "ms-toolsai.jupyter", "ms-vscode.powershell", "HashiCorp.terraform", "eamodio.gitlens", "GitHub.copilot-chat" ] } } }
-
Take your development environment anywhere and on any machine with Dev Containers.
there are already built docker images for common development environment. You can either use one of them, or build one from Docker file. Using a pre-built dev container doesn't mean you are only limited to that image, because you can still add other tools, which they are called features to that image. For a list of the pre-built templates check here, and for the other features that you can add check this. You don't need a Docker file, unless you want to build your dev environment step by step.
-
VSCode & GitHub Codespaces for my Python playground
// For format details, see https://aka.ms/devcontainer.json. For config options, see the // README at: https://github.com/devcontainers/templates/tree/main/src/python { "name": "Python 3", "image": "mcr.microsoft.com/devcontainers/python:0-3.11", "features": { "ghcr.io/devcontainers/features/python:1": {} } // Features to add to the dev container. More info: https://containers.dev/features. // "features": {}, // Use 'forwardPorts' to make a list of ports inside the container available locally. // "forwardPorts": [], // Use 'postCreateCommand' to run commands after the container is created. // "postCreateCommand": "pip3 install --user -r requirements.txt", // Configure tool-specific properties. // "customizations": {}, // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. // "remoteUser": "root" }
-
Containerizing devops tools with docker compose
This is actually very easy. I've implemented a number of tools like this publicly but the standard doesn't limit you to public stuff. I can't emphasize enough the amount of speed we gained when we implemented this standard. https://containers.dev/features
-
DevContainers for Azure and .NET
features: While you can add everything in Dockerfile for the build, there are already pre-configured features you can optionally add. You can find the complete list of the features at here. Some examples of those features are common utilities and tools like Azure CLI, GitHub CLI and Terraform, and languages like node.js, Java, .NET, Python, etc.
nvim-dev-container
-
Dev Containers: Open, Develop, Repeat...
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.
-
DevContainers - Vscode Alternative
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.
- remote-sshfs.nvim: Explore, edit, and develop on a remote machine via SSHFS with Neovim and telescope. Loosely based on VSCode's Remote -SSH (very alpha, rapid development)
-
Neovim and devcontainers
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.
-
Looking for devcontainer solution in neovim
esensar/nvim-dev-container
- Neovim + Docker?
-
I have just published nvim-dev-container plugin
nvim-dev-container provides functionality related to devcontainer.json file, similar to VSCods's remote container development.
What are some alternatives?
templates - Repository for Dev Container Templates that are managed by Dev Container spec maintainers. See https://github.com/devcontainers/template-starter to create your own!
lazydocker - The lazier way to manage everything docker
spec - Development Containers: Use a container as a full-featured development environment.
lspcontainers.nvim - Neovim plugin for lspcontainers.
devcontainers-dotnet.
vscli - A CLI/TUI which makes it easy to launch vscode projects, with a focus on dev containers.
images - Repository for pre-built dev container images published under mcr.microsoft.com/devcontainers
remote-sshfs.nvim - Explore, edit, and develop on a remote machine via SSHFS with Neovim
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
devc - cli tool to manage your devcontainers
zsh-autosuggestions - Fish-like autosuggestions for zsh
.dev-env-docker - Development Environments Inside Docker Container