DevBox allows you to declare the list of tools required by the project via the devbox.json file and run the devbox shell. Everyone working on the project gets a shell environment with exactly the same version of these tools. The development environments that are created are isolated from everything else on the laptop. It can create isolated environments right on your laptop, without an extra layer of virtualization that slows down the file system or every command. When you’re ready to stream, it will convert it into an equivalent container; But not before.
In the event the user is working on several projects, all of which need different versions of the same binary, instead of trying to install conflicting versions of the same binary on the laptop, it is possible to create an isolated environment for each project and use a copy of his choice for each of them.
Devbox analyzes the source code and instantly converts it into an OCI compliant image that can be deployed to any cloud. According to its maintainers, the image is optimized for speed, size, security, caching… and without having to write a Dockerfile. And unlike buildpacks, they will do it quickly. Remember that the OCI standard is a standard that allows the exchange of catalog data records for product search and selection between management systems.
Applications often need the same set of dependencies when developing on our laptop and when compiling them as a cloud-ready container. Devbox development environments are similar: this means that the user can turn it into a local shell environment or a container ready for deployment in the cloud.
Install Devbox
In addition to installing Devbox itself, nothing And the docker It must also be installed since Devbox depends on it:
- Install Nix Package Manager.
- Install Docker Engine or Docker Desktop. (Docker is only needed if the user is creating containers – the shell function works without them.)
- Devbox installation:
curl – FSSL https://get.jetpack.io/devbox | crush
Fast and inevitable shell
Create a development structure with specific tools installed. These tools will only be available when using this Devbox shell, so as not to spoil the device.
Open Terminal in a new empty folder.
Devbox Configuration:
init devbox
This creates a file devbox.json in the current directory. You must stick to source control.
Add command line tools from nothing packages. For example, to add to Python 3.10:
devbox add python310
your profile devbox.json Keeping track of the packages you added, it should now look like this:
1 | { "paquets" : [ "python310" ] } |
Start a new structure with these proven tools:
[C=shell]devbox shell[:C]It is possible that you are in a Devbox shell (and not in a regular terminal) because the shell and directory have changed. In this example, we have installed Python 3.10.
Using Python 3.10
Python - version
Your usual tools are also available, including environment variables and configuration settings.
git config - get user.name
To exit the Devbox shell and return to the usual shell:
Exit
instant docker image
Devbox makes it easy to package the application as an OCI compliant container. Devbox analyzes the code, automatically identifies the toolkit needed for the project and builds it into a Docker image. It is recommended
- dInitialize the project with devbox init to build the image;
- To build the image: build devboxThe resulting image is called devbox.
- Tag the image with a more descriptive name:
[C=shell]docker tag devbox my-image: v0.1[C]
Devbox currently detects Go and Python languages.
source : DevBox
And you?
What do you think about the matter?
Given the plurality of development tools, do you find a tool like DevBox necessary?
See also:
“Hardcore beer fanatic. Falls down a lot. Professional coffee fan. Music ninja.”
More Stories
SALES / PHOTO SALES – Nikon D850 “5 Star” Bare Body Photo Body at €2,539.00
Discovering a new turning point under the Antarctic ice sheet! What are the consequences?
Record number for an insect!