cli
just
cli | just | |
---|---|---|
10 | 170 | |
1,325 | 18,036 | |
6.3% | - | |
8.9 | 9.4 | |
7 days ago | 2 days ago | |
TypeScript | 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.
cli
-
Show HN: Lapdev, a new open-source remote dev environment management software
You still cannot stop, remove or update a Dev container from CLI and there at numerous issues with the rest of the implemented features.
[0]: https://github.com/devcontainers/cli?tab=readme-ov-file#cont...
-
Launching dev containers from code - is impossible?
Well, I got the hint from this GitHub issue. Also, it seems like at one time a devcontainer open command existed in the old dev container CLI (it does not exist anymore since the CLI wants to be editor-agnostic).
-
Dev Containers: Open, Develop, Repeat...
So you can use Dev Containers from the vscode user interface rather intuitively. All configurations can also be edited directly and there is even a CLI. However, this CLI is made editor agnostic, so there is no vscode integration.
-
Devcontainer CLI in Neovim
During the last past few days I've been working on a new neovim plugin: nvim-devcontainer-cli which gives you the possibility to build, run and connect to your Docker devcontainer using devcontainer-cli, which is the CLI used by the VS Code Devcontainer plugin.
-
DevContainers - Vscode Alternative
While doing a bit more research: https://github.com/devcontainers/cli and https://devcontainers.github.io/
-
Devcontainers without VSCode
If you want to support both use-cases (vim/Neovim & vscode), then vscode/MS broke out devcontainers feature from vscode into a separate project to support non-vscode users. Check out https://github.com/devcontainers/cli and https://devcontainers.github.io/
-
Are there better options for standardizing development environments than VS Code dev containers?
It's hard to ensure that a prebuilt image provides valid cache for the dev container (I actually submitted a PR to help with this, but I'm still seeing problems and haven't figured out why yet). When we have a cache miss, the build takes 10 minutes.
-
Creating a dev 'container' to make it easier on first timers
to add this this they recently defined "devcontainers" as a spec to help integrate it with other editors and also turn it into a CLI tool that is being heavily worked on https://containers.dev/ https://github.com/devcontainers/cli
-
Developing inside a Container using Visual Studio Code Remote Development.
the team have actually started developing devcontainers an an open specification for other IDEs to start integrating with along with a CLI tool they are developing to cutout the need for VS code all together. https://github.com/devcontainers/cli
-
Ask HN: Any Good Make Alternatives?
Haven't tested it myself, but there's now a cli to decouple devcontainers from VSCode:
https://github.com/devcontainers/cli
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?
vscli - A CLI/TUI which makes it easy to launch vscode projects, with a focus on dev containers.
Task - A task runner / simpler Make alternative written in Go
vscode-remote-release - Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
cargo-make - Rust task runner and build tool.
spec - Development Containers: Use a container as a full-featured development environment.
cargo-xtask
lapdev - Self-Hosted Remote Dev Environment
Taskfile - Repository for the Taskfile template.
.dev-env-docker - Development Environments Inside Docker Container
CodeLLDB - A native debugger extension for VSCode based on LLDB
template-python
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.