nvim-dev-container
just
nvim-dev-container | just | |
---|---|---|
7 | 169 | |
504 | 17,633 | |
- | - | |
7.9 | 9.0 | |
11 days ago | 4 days ago | |
Lua | Rust | |
MIT License | Creative Commons Zero v1.0 Universal |
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.
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.
just
-
I stopped worrying and loved Makefiles
I don't like makefiles, but I've been enjoying justfiles: https://github.com/casey/just
- Just a Command Runner
-
Ask HN: Any tool for managing large and variable command lines?
I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.
Define your recipes and then you can compose them as needed.
[0] https://github.com/casey/just
-
Ask HN: What software sparks joy when using?
just - https://github.com/casey/just
-
GitHub switched to Docker Compose v2, action needed
Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.
I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.
That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]
[0]: https://github.com/casey/just
-
Which command did you run 1731 days ago?
> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin
I would consider using just for this:
https://github.com/casey/just
-
Using Make – writing less Makefile
Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.
For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.
[1] https://github.com/casey/just
-
Show HN: Just.sh – compiler that turns Justfiles into portable shell scripts
This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:
https://github.com/casey/just/issues/429
I really wish just was included as a package in distributions.
-
Sharing Saturday #496
So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.
-
What’s with DevOps engineers using `make` of all things?
i've grown to like this for my personal projects. https://github.com/casey/just
What are some alternatives?
lazydocker - The lazier way to manage everything docker
Task - A task runner / simpler Make alternative written in Go
lspcontainers.nvim - Neovim plugin for lspcontainers.
cargo-make - Rust task runner and build tool.
vscli - A CLI/TUI which makes it easy to launch vscode projects, with a focus on dev containers.
cargo-xtask
remote-sshfs.nvim - Explore, edit, and develop on a remote machine via SSHFS with Neovim
Taskfile - Repository for the Taskfile template.
devc - cli tool to manage your devcontainers
CodeLLDB - A native debugger extension for VSCode based on LLDB
.dev-env-docker - Development Environments Inside Docker Container
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.