System Settings
Settings that apply to the whole instance.
System > Settings holds the settings that apply to every team. It is for people who can manage the instance.
The Email and Network pages are covered on their own: Email and Network Isolation.
Wildcard Domain
Services get their generated domains under this domain. With unbind.example.com here, a new service gets something like api-k3x9pa.unbind.example.com.
Point a wildcard DNS record at your server before saving. The page shows the IP address to use. See DNS Setup.
Changing it affects new generated domains only. Domains that services already have stay as they are.
Builds
| Setting | What it is | Range |
|---|---|---|
| Replicas | How many build workers run at once | 1 to 10 |
| Parallelism | How many build steps each worker runs at the same time | 1 to 32 |
Builds are the heaviest thing Unbind does. They compete with your running services for CPU and memory.
- One small server: keep both low. A build that takes a little longer beats a site that slows down.
- Several servers: raise Replicas, but not above the number of servers.
If the build service is managed outside Unbind, these settings are shown but cannot be changed.
Registry
System > Settings > Registry manages the registry that stores your built images. Images and build caches share one volume, 20 GB by default.
Usage
The bar shows how full the volume is, with a mark at the cleanup threshold. Usage going up to the threshold is normal: cleanup brings it back down.
Cleanup
Cleanup runs every hour. When usage is over the threshold, it first deletes what nothing points at anymore: every build overwrites the build cache of the one before it, and the old cache stays on the volume until cleanup removes it. If usage is still over the threshold, it deletes the oldest images until usage is under it again. It never deletes:
- Images that are deployed, including stopped services and cron jobs between runs
- Images pushed in the last hour
- The newest image and the newest build cache of each repository
Cleanup waits until no build is running before it deletes anything. Builds never wait for cleanup. If a build starts while cleanup is deleting and part of its image gets removed, the build notices and pushes the image again.
The page shows the last run: how much space it freed and how many images and overwritten caches it deleted. Still over the threshold means everything left is protected, so grow the volume.
Clean Up Now runs cleanup right away and deletes every image it is allowed to delete, even when usage is under the threshold. Redeploying a deployment whose image was deleted builds it again.
Settings
| Setting | What it is | Default |
|---|---|---|
| Threshold | Usage at which cleanup starts deleting images | 16 GB |
| Schedule | How often cleanup checks the registry | Every hour |
| Size | Size of the volume. It can grow but never shrink. | 20 GB |
The size can only be changed when the storage behind the volume supports growing. Growing it asks you to confirm, since it can't be undone. The page shows Expanding the volume until the new size is ready, which can take a couple of minutes.
People who can manage the instance get a notice in the app when the registry is almost full or cleanup can't free enough space.
If you chose an external registry at install, Unbind doesn't manage it and this page only says so.