Skip to main content
These examples install products on the Rigbox base environment and freeze their installation into an image. They require v0.13 and explicitly select image deployment.

​
Choose a product

The example manifests declare a data volume and select workspace.deployment.strategy: image. reproducible: true freezes the installation; it does not make unpinned upstream downloads reproducible across time. Review installers and version pins before production use.

​
Deploy locally

Install the CLI, sign in, and use a new test workspace. Clone the examples, then choose one directory:
For Gitea or n8n, change the directory in the command. Record the resulting workspace/app IDs and URL. A subsequent image change can require --reimage, replacing the workspace root filesystem. Back up data and verify volume mounts before consenting.

​
Verify and access

Open the reported route and complete the product-specific setup. Create a test file, repository, or workflow and verify it after an application restart. This does not establish backup recovery or image-upgrade compatibility. All three manifests default to a private Rigbox route. code-server disables its own password authentication in this example, so keep the authenticated Rigbox route or configure code-server authentication before changing visibility. Review each product’s user management independently. If installation fails, inspect the build ID’s output with rig build logs BUILD_ID. n8n has larger memory and disk requirements than the other examples. Do not repeatedly retry an out-of-memory installation without reviewing resources.

​
Clean up

Export files, repositories, or workflows you want to keep. Delete only the test workspace and inspect its persistent storage separately:
See Images and templates and Persistent volumes before hosting important data.