Repository navigation
FossFLOW: store diagrams on the host - #365
Merged
Merged
Conversation
4 tasks done
Add a volume for /data/diagrams, where FossFLOW saves diagrams on the server. The stack had no volume, so saved diagrams were lost when the container was recreated. Add upgrade steps to the README for existing installations.
jackspiering
force-pushed
the
fossflow-persist-diagrams
branch
from
October 8, 2026 15:26
db44b3b to
884133c
Compare
crypt0rr
approved these changes
Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
FossFLOW saves diagrams on the server in
/data/diagrams(ENABLE_SERVER_STORAGE=trueis the default of the image). The stack had no volume, so every saved diagram was lost when the container was recreated, for example after an image update.compose.yaml: add the volume./${SERVICE}-data/diagrams:/data/diagrams.README.md(service): list the data folder, remove the data-loss warning, and add an "Upgrading" section that explains how to copy existing diagrams out of the container first.Related Issues
Verification
Tested in a scratch copy with
stnsmith/fossflow:latest. A stand-in container replaced Tailscale, because the test only concerns the volume. Diagrams were saved and listed through the API on port80(POSTandGET /api/diagrams), the same path that the web interface uses.maindocker compose down, thenup -d./fossflow-data/diagramsUpgrade path from the README, starting on
mainwith one saved diagram:mkdir -p fossflow-data/diagramsdocker cp app-fossflow:/data/diagrams/. ./fossflow-data/diagrams/docker compose up -dwith the file from this branchResult: the diagram from the old container is listed, next to a new one that was saved afterwards.
docker compose config --quietinservices/fossflow: passed.rumdl check --config .markdownlint.yml services/fossflow/README.md: passed.git diff --check: passed.Not tested: access through the Tailnet, which this change does not touch.
Checklist
Additional Context
stan-smith/FossFLOWno longer exists on GitHub. The imagestnsmith/fossflowis still on Docker Hub, andAbrar74774/FossFLOWcontinues the project. Whether the stack should move to another image is a separate question.