John Lago
John Lago
We'll look into this! We're evaluating how to let users configure alternative Nix repositories and package sources for Devbox.
Thanks for this request. This could work via a `--platform` flag that is passed to Docker when building the image
Supportable with the workflow described above for nodePackages and some other package managers. For tools like Bundler, there are some workarounds that can be found in our examples Repo (https://github.com/jetpack-io/jetpack-examples)....
Hey @Satont! We're working on turning this on for an upcoming release, so that developers can manage the version directly in their `devbox.json`. I think this will be out in...
This should be addressed in #227
Closed with #227
`--config` flag was added in a previous PR, but as of right now we are not planning to allow the renaming of `devbox.json`
Closing this issue since Devbox no longer builds containers directly. Dockerfiles + Devcontainers can now be generated using `devbox generate dockerfile` or `devbox generate devcontainer`.
Closing this issue out, as we have deprecated `devbox build`. Developers can now generate a Dockerfile for their project using `devbox generate dockerfile`, and build the container with the tool...
Closing this since we can now generate a `.envrc` file for Devbox. There's a second issue in here around better VSCode integration, which I will file as a separate issue.