Skip to main content

​
Pulling Packages from the Cache​

Once you have authenticated, Devbox will automatically configure your cache for you. You can also manually configure the cache by running: 
devbox cache configure
Once configured, Devbox will attempt to use the cache whenever you run a command that prompts Devbox to install a package in your project. When installing a package, Devbox will check for a cached binary in the following locations:
  1. Your local Nix Store /nix/store
  2. The Jetify Cache
  3. The Public Nix Cache (cache.nixos.org)
If the package is not available in those locations, then it will build the package from source.

​
Pushing to the Cache​

You can push custom packages and project closures to your Jetify Cache directly from the Devbox CLI. Push access is currently only available for authenticated users with Admin permissions.

​
Pushing a Devbox Project​

You can push the entire closure of a Devbox project to the Jetify Cache by navigating to your project root and running 
devbox cache upload

​
Pushing a specific package​

You can also push a single package by passing a flake reference to the Devbox CLI. For example, to push a custom mongodb package from a custom flake.nix on your machine, you can run: 
devbox cache upload path:./path/to/flake.nix#mongodb
You can also cache packages from Github or from Nixpkgs by passing the appropriate Flake reference. This can be useful for caching build artifacts if a package does not exist in the public Nix cache, or if it requires you to build it from source: 
# Cache an installable hosted on Github (process-compose)devbox cache upload github:F1bonnac1/process-compose# Cache a package from nixpkgsdevbox cache upload nixpkgs#mongodb
⌘I