2 November: a hard disk limit per workspace, and the editor on its own address
Every workspace now has its own disk limit with usage shown in the container view, and the web editor of a container runs on a separate address that carries none of your site session.
Wenn du Container nutzt, siehst du Speicherverbrauch und Limit und wirst bei 90 Prozent gewarnt, und der Editor öffnet auf einer eigenen Adresse. Prüfe deinen Verbrauch, sonst ist nichts nötig.
Two of the Strix findings from the scans of 28 October were closed in code on 2 November. Both are visible in the container view.
Text version
U31: workspaces had no filesystem quota, now each has its own disk image with usage shown. U06: the editor ran under the main address, now each container has its own address without the main session.
Disk limit per workspace
Workspace folders had no filesystem quota. The disk watchdog only saw the free space of the whole host, so one tenant could have filled it. Each workspace now gets its own disk image, set up when the container starts and, for stopped containers, by a background job. The container view shows your usage and limit and warns the owner at 90 percent.
The editor on its own address
The web editor ran under zerolog.ch/ide/, so script from inside a container ran with the session of the person looking at it. Each container now gets its own editor address. Cookies on it belong to that address only, and none of the main site session reaches it. You get in through a single-use link valid for 30 seconds. Rights are checked again on every request. The old address only redirects. This closes the finding that the Strix entry lists as contained.
Bookmarks to the old editor address still work through the redirect.