v0.4.13

Added

• Choose which domain a workspace subdomain is published under. Settings has a Base domains section: add a suffix, mark one as the default, rename one, or remove one you no longer use. A deployment used to have exactly one suffix for app subdomains, fixed at install time in config.yaml, and changing it meant re-running the installer over SSH.

  Renaming a base domain moves every subdomain published under it at once, and no workspace restarts — app subdomains are routed from Traefik's file provider, not baked into the container. Where a deployment has more than one suffix, the create and detail pages let you pick per subdomain, so two workspaces can each publish "api" under different domains. Deployments with a single suffix see no picker and nothing changes for them.

  Your installed domain is kept: it seeds the list on first boot and is then left alone, so re-running the installer cannot revert a list you have edited in Settings. Existing subdomains keep routing exactly as before.

• Install without the workspace image. The installer takes --workspace-image=no, which brings up the server, dashboard and API without downloading the ~750 MB workspace image — around 45 MB and a couple of minutes instead of the better part of a gigabyte and twenty. Everything except creating a workspace works, and when you want the image, re-running the installer with --workspace-image=yes downloads that image and nothing else.

  Most useful when you are standing a host up to look at it, testing an upgrade, or working on a small disk. The answer is remembered, so an upgrade will not quietly start — or stop — fetching it, and --dry-run tells you which way the next run would go. While there is no image the closing banner says workspace image: NOT INSTALLED, and trying to create a workspace names the command that fixes it rather than failing cryptically.

Fixed

• Upgrades no longer abort claiming they introduced foreign-key violations. A migration that rebuilds a table to add a foreign key renumbers the ones already on it, and the integrity check read the pre-existing orphans it had merely copied as damage it had just done. It now keys violations on the tables involved, so an upgrade is judged on what it actually changed.