Skip to main content
One service data directory stores all your Flowfield workspaces. The default is ~/.flowfield on macOS and Linux. Project repositories and installed native harness configuration remain separate. Choose another data directory with FLOWFIELD_DATA_DIR or flowfield --data-dir /absolute/path serve. This changes the service’s store, not an individual workspace’s repository locations. Inspection copies remain after completion or archiving. Deleting a task removes its copies and files; stop previews and save useful edits first. Adopted repositories and delivered code remain intact.

Updating and recovery

Follow the update commands to upgrade while preserving your workspaces and settings. Queues start paused unless Auto-start worker queue is enabled. Interrupted workers may need recovery.

Recovery

If startup reports an unsupported database version, use a Flowfield build compatible with the reported schema. Automatic database recovery copies are stored under backups/ in the data directory. For a manual restore, stop the service and restore the saved data directory using its matching Flowfield version. For historical upgrade requirements, consult the release notes. To use a separate data store, select a new directory with flowfield --data-dir /absolute/path/to/new-flowfield-data serve.

Inspect storage

This command runs offline without creating or modifying application data:
Add --json for structured output. To inspect another store, place --data-dir /absolute/path before storage.

Full backups

Stop the service and copy the entire data directory and relevant project repositories. A database copy alone omits submitted files. Restore using a compatible Flowfield version. Native accounts and session data belong to each harness and need separate backups for native continuation.