01 / THE ROLE
In this lab.
The lab hosts an Excalidraw-compatible application as a containerised service. The current runtime uses a persistence-oriented image; its exact drawing-storage behaviour must be understood from that deployment rather than assumed from the generic upstream application.
02 / THE CONNECTIONS
Follow the flow.
- STEP 01Browser drawing
- STEP 02Application service
- STEP 03Configured persistence
- STEP 04Export or continued editing
03 / How it works
How it works.
The useful output is an editable visual explanation or an exported diagram. How a drawing survives a browser refresh, server recreation or a different client session depends on the implementation. Public diagrams on this website are deliberately authored, sanitised illustrations rather than exports of a private operational canvas.
04 / Persistent data & recovery
Persistent data & recovery.
Classify which drawings are unique and where their editable source is stored. Keep intentional exports and source artefacts together when needed. Rebuilding the container alone may not recover drawings, and an image name is insufficient proof of persistence.
05 / How to check it
How to check it.
For acceptance, create a neutral drawing, test the expected save/reopen behaviour and export it. Confirm the behaviour across the failure or recreation scenario being considered. A served JavaScript frontend proves only that the application assets are reachable.
06 / Decisions & limits
Decisions & limits.
Diagrams are useful when they explain a relationship. They should not imply exact network paths or live health unless those are actually the subject and have been verified.