spec
cli
spec | cli | |
---|---|---|
48 | 10 | |
2,814 | 1,242 | |
4.1% | 3.6% | |
7.0 | 8.9 | |
8 days ago | 7 days ago | |
TypeScript | ||
Creative Commons Attribution 4.0 | 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.
spec
-
Show HN: Lapdev, a new open-source remote dev environment management software
Hi, Lapdev dev here. Let me try to answer your question.
It's installed on a remote server so it provides remote environments. If you use VSCode remote, then you can "open" it through VSCode remote ssh.
The environment that Lapdev provides essentially is a container (other format is on the roadmap) with things pre-installed as defined in Devcontainer(https://containers.dev/) format.
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
Happy to take this one, as I am one of the cofounder of Daytona.
Daytona solves all the automation and provisioning of the dev environment, actually wrote an article here laying out exactly what we do: https://www.daytona.io/dotfiles/diy-guide-to-transform-any-m...
Daytona currently supports only the dev container (https://containers.dev/) "dev env infrastructure as code" standard, but are looking to support others such as devfile, nix and flox.
Hope this helps
-
A Journey to Find an Ultimate Development Environment
The full usage of the container means that you'll do the development inside the container. All the tools for development need to be installed inside the container. One of the technologies that leverage this approach is Devcontainers.
-
How CDEs work - no bs blog post
Two standards for CDE configuration exist: devfile.yml and devcontainer.json. Both assume that the CDE is a single container and allow specification of which tools should be deployed to this container, as well as a reference to scripts that should run after the container has been created.
- Use Docker to create a local development Python environment
-
Launching dev containers from code - is impossible?
... is how I introduced the concept of dev containers in my last article.
-
Dev Containers: Open, Develop, Repeat...
How it works? Dev Containers is a specification based on Docker. This specification describes a metadata file (devcontainer.json), which defines how the project (Docker container, IDE settings, plugins, etc) is set up.
-
Try MongoDB and Laravel in 1-click via GitHub Codespaces
Codespaces is built to run Dev Containers, an open standard for Development Containers. The Dev Container will reference a Docker build file, which describes the software and services our app is running on. It also defines things related to our development environment, including IDE plugins, network ports, and more.
-
Is there some catch to cause DNS issues on Linux, that is not common with Windows or Mac?
I was using Devcontainer with VS Code. In a part of the container build process, DNS lookup seemed to be failing in Debian 12. BTW, the container image was based on Debian 11. I probably tried it about 10 times in total, so I'm pretty sure it persisted, not an one time error. I noticed the build process was failing because the process failed to find some domains, with an error message like could not resolve host github.com. Some domains I noticed was github.com and ghcr.io, so it failed sometimes for one domain, and sometimes for the other.
-
Dev Container for React Native with Expo
// For format details, see https://aka.ms/devcontainer.json. For config options, see the // README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node { "name": "Node.js & TypeScript", // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile "image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bullseye", // 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": [8081], "initializeCommand": "bash .devcontainer/initializeCommand.sh", // Use 'postCreateCommand' to run commands after the container is created. "postCreateCommand": "bash .devcontainer/postCreateCommand.sh", // Configure tool-specific properties. // "customizations": {}, // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. // "remoteUser": "root", // "containerEnv": { // }, // "remoteEnv": { // "DEV_USER_HOST": "${localEnv:USERNAME}" // }, "runArgs": ["-p=8081:8081", "--env-file", ".devcontainer/.env"] }
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
What are some alternatives?
features - A collection of Dev Container Features managed by Dev Container spec maintainers. See https://github.com/devcontainers/feature-starter to publish your own
vscli - A CLI/TUI which makes it easy to launch vscode projects, with a focus on dev containers.
features - A collection of development container 'features' for machine learning and data science
.dev-env-docker - Development Environments Inside Docker Container
conda-devcontainer-demo - Mini Conda + Mamba dev container setup to make working with environments easy.
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.
tweek - Tweek - an open source feature manager
nvim-devcontainer-cli
lapdev - Self-Hosted Remote Dev Environment
nvim-dev-container - Neovim dev container support - Mirror of https://codeberg.org/esensar/nvim-dev-container
microservice-rust-mysql - A template project for building a database-driven microservice in Rust and run it in the WasmEdge sandbox.
template-python