Getting Set Up For a Local Event

Prepare your development environment

If you have not already done so, please follow the first step in the Get Started guide which asks you to run the script. Then you should come back to this page and configure the local cache before proceeding with verifying your Nix setup in the quick start guide.

The rest of this guide assumes you have either done this or created an equivalent environment manually.

Configure Nix to use a local cache

The quick start script configures Nix to use as a cache. This significantly speeds up launching the Holonix development environment. It works well for individuals, but at live events it requires a lot of bandwidth with multiple people downloading large amounts of files at the same time. To improve the experience for everyone, a cache can be provided locally. This section shows you how to connect to the local cache.

The event hosts need to provide you with a cache name. This will be unique per event! Replace <event-cache-name> with the provided name in the command below.

At a command line:

bash <(curl use <event-cache-name>

The script will tell you what it’s changing and may ask for confirmation for some changes. It may also prompt for your password if it needs to make changes to files owned by the root user.

At the end of the event, you shouldn’t keep these configuration changes. You can run another command to remove all the configuration that the first command added.

At a command line:

bash <(curl cleanup
It looks like you are using Internet Explorer. While the basic content is available, this is no longer a supported browser by the manufacturer, and no attention is being given to having IE work well here.