1.4.47
Stores: name, keep and switch a workspace’s data
Freeze a workspace’s databases into a named store, keep as many as you like, and restart any workspace on one of them — or on a clean slate — without changing what anyone else starts from.
New
- DesktopFreeze asks for a name and saves the workspace’s images and databases as a new store. The workspace restarts on it; new workspaces keep starting from the project’s default until you choose otherwise.
- DesktopSwitch restarts a workspace on any of the project’s stores, or on Clean. It warns you before throwing away database changes since the last restart, and offers to freeze first. Your code is never touched.
- DesktopThe Compute tab lists every store with its size and what’s inside it. Rename one, make it the default for new workspaces, or delete one nobody uses to get the disk back.
Improved
- DesktopThe Environment panel is one view: a tile for everything your workspace runs, coloured by what it is doing. Press a tile to open its port. A process still building says so instead of looking broken, and a stop that hangs offers Force stop.
- DesktopA process’s log opens as a document with a filter, Follow and Clear, and its own Start and Stop.
- DesktopWhen .berth/actions.toml has a mistake, the panel tells you what it is and on which line, including anything it no longer reads, such as [[actions]].
- DesktopArchive lives in the Compute tab, and archived workspaces no longer fill the workspace list.
- DesktopPadar no longer starts the extra services in .berth/compose.yaml. Start your project’s databases from .berth/actions.toml, so a frozen store keeps their data.
- MobileThe phone’s Environment screen matches the desktop: the same tiles and logs, and Freeze and Switch from the Store sheet.