Skip to content

History / Security Model

Revisions

  • The wiki catches up with 1.5 beta 5: Tasks, form buttons, Suggestions tabs, Add Service, vulnerability reports, Greta (experimental), the list redesign and host tabs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Oct 20, 2026
  • The wiki catches up with 1.5 beta 4: the fleet, notifications, Kubernetes and more Every existing page keeps what is still true and gains what changed since 12 September (Dashboard is now Overview; Go To, the search grammar, groups, registries, pushing to hosts, the Helper, the wire). Nine new pages: Hosts, Notifications, Kubernetes, DNS, Registries, Groups and Suggestions, Sharing and Export, Updates, and the Flotilla Helper. Checked against the code. Drafted by Iris, deepened by Sonny, reviewed by Andy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Oct 12, 2026
  • Flotilla keeps its capital F again Reverts the lowercase change: only the app's drawn wordmark is lowercase (the owner, 10 October). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Oct 10, 2026
  • flotilla is written lowercase, like the logo Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Oct 9, 2026
  • docs: correct the wiki against the app it describes An independent review by a second model family read the wiki against the source and found twenty factual errors. It was right about essentially all of them, and the cause was the same in every case: I wrote from the project's own narrative documents rather than from the strings the app actually shows. The two that mattered most: Import Flotillafile… lives in the machine create form and is machine-only. It loads the *first* machine into the fields and names what it left behind. The containers in a Flotillafile are parsed and validated but nothing consumes them yet. The page had described a general import that populates run forms, which does not exist. Settings has six tabs and twenty-two rows. The page described a handful, and invented labels for two of them — the real controls are "Show Dock icon" and "Binary path". Rewritten from the registry. Also corrected: Restart is not present on a stopped row; single-item deletion does *not* always ask, it honours the preference and the page contradicted itself in consecutive sentences; the copy menu offers Name, Image, IP Address and Port URL rather than the three things claimed; containers and stats poll on two separate intervals; the dashboard table holds running containers only; the logs feed covers running sources only; volumes and networks have Inspect sheets rather than embedded details; the create-network form does support IPv6 and plugin options, which the page said it did not; the machine save messages are "Saved — applies on next start" and "Saved — still running on the previous values"; the port link is "Open"; the bulk bar shows plain verbs with the count beside them. Missing features now documented: a Menu bar and window page (the popover, the per-item controls, Needs attention, the sidebar rail, appearance cycling); the Run form's Command, Detach, and resource overrides; the build form's Dockerfile path, target stage, platform and cache flag; machine Edit Settings…, Set as Default, Apply and Restart, Mount Home Read-Write and the boot-log selector; the Activity filters and the collapsible strip; dashboard ranges and Needs attention; the log tab's Timestamps, Wrap, Follow and Reload; Files breadcrumbs, Copy path, Replace and the not-running state; shell tab Rename; and the image, volume and network filters. Roadmap: the review also flagged that the security page named the reserved policy type and its one current value. Generalised — the boundary is described, the naming is not. 21 pages, 1370 lines. All links resolve, every page reachable from the sidebar, and the labels are spot-checked against the source. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Sep 5, 2026
  • docs: document what was actually built, and stop hinting at what is not Five new pages and a reorganisation. The previous version documented the sidebar sections and skipped most of the actions inside them, which meant the wiki described where things are without describing what you can do. New: - Images — pulling, building from a Dockerfile (and why the file panel is the authorisation for it), tagging, pruning, running a container from an image, and what the run form's live command preview is for. - Volumes and networks — creating both, how a mount is spelled, why a named volume differs from a host path, and why the built-in network's delete button is disabled rather than spinning. - Files — browsing a container's filesystem and copying files in and out, with the naming deliberately "copy out of the container" rather than "download". - Flotillafile — the declarative format, its full schema, its six structural limits, and the point that importing one creates nothing: it yields pre-filled forms you still confirm, and the parser follows no paths, files or URLs. - Views and filtering — table versus cards, columns, filter, search, sorting, multi-select and bulk actions, and why Copy beats Open in browser on a published port. Containers now points at those rather than half-repeating them, and lists what each of its seven detail tabs holds. Removed: every mention of how remote host management will work. The transport, the discovery mechanism and the authentication model are gone from the wiki, and the FAQ now says only that it is planned for a later release and that nothing listens today. Publishing a design before the implementation exists gives it away for nothing. 20 pages, 1224 lines. All internal links resolve and every page is reachable from the sidebar. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Sep 5, 2026
  • docs: the Flotilla wiki Thirteen pages covering install, first run, each section of the app, the security model, building from source, troubleshooting and an FAQ. Written from verified behaviour rather than from the feature list: the machine images that actually boot, why memory differs from Activity Monitor, why logs do not follow, why eight settings are disabled and what each one says, and why the terminal is a capability boundary rather than a convenience. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @melonfleet melonfleet committed Sep 5, 2026