spec VS asdf-nodejs

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.

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

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.

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.

... is how I introduced the concept of dev containers in my last article.

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.

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.

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.

// 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"] }

Not nix based, but I really like https://github.com/jdx/mise too to manage dev tools.

It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.

That's what I would suggest as well. WSL2 and use asdf[1] to manage the erlang/elixir versions.

[1]: https://github.com/asdf-vm/asdf

echo "Installing nodejs with asdf" asdf plugin add nodejs https://github.com/asdf-vm/asdf-nodejs.git asdf install nodejs latest asdf global nodejs latest

However this is still a neat script OP! I was looking for something like this when installing Go for the first time and was contemplating between goenv, gvm, and asdf before settling on brew.

Have you tried this? https://github.com/asdf-vm/asdf-nodejs#nvmrc-and-node-versio...

Also lts, lts-hydrogen, etc are available to install I can see when running `asdf list all nodejs`

How does this compare to nvm or asdf?

I'm not too familiar with installing Ruby on Mac, but you could try using a ruby version manager (like rbenv or asdf).

For more information, or if you need help on this awesome tool, don’t hesitate to head over to asdf-vm.com. Also, feel free to star the GitHub Repository of asdf to support the team behind this project. 😉

nvm was adding a huge delay to my shell startup and starting node. There are faster ones out there like n https://github.com/tj/n or fnm https://github.com/Schniz/fnm I use fnm there are also similar tools that work with multiple languages like asdf https://github.com/asdf-vm/asdf

Now, what you want is to have multiple Python versions installed in your system. The most used way on Linux is pyenv, I think. Another one that I found is asdf. I'd try that before pyenv because pyenv is a bit quirky to install.