aleleba/figcraft
1
0
Fork 0
mirror of https://github.com/storytold/figcraft.git synced 2026-10-28 12:26:52 -06:00
Code Issues Packages Projects Releases Wiki Activity

fix(server): keep each team library version in its own file (#206)

Browse Source
This commit is contained in:
MarekSpodBiedry
2026-10-14 16:19:01 +02:00
parent 833f0d2c27
commit a8a689d682
4 changed files with 74 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/collab-protocol.md
+4 -2
View File
@@ -726,8 +726,10 @@ resuming with its offline edits, and leaving the session going back to snapshot
- **What is kept.** The published library a library file holds (manifest and snapshot with
per-asset versions) travels as a small `.figcraft` archive holding only it. The server reads it
in full with the limits a library file is read with, requires the file's library id once one is
kept and a newer version, then writes it beside the file (`library.bin`, atomically) and records
id, name and version in the file's description. Publishing from the app first fetches the
kept and a newer version, then writes it beside the file in a file of its own
(`library-<version>.bin`, atomically) and only then records id, name and version in the file's
description, so a failed write or a crash in between leaves the previous version served whole;
the previous version's file is deleted after. Publishing from the app first fetches the
server's version and publishes the next one from it, so per-asset versions continue whoever
published last; a race is refused and the next publish follows.
- **Using it.** A file enables the library with the link in place of a library file's path