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>
flotilla is written lowercase, like the logo
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
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>