How baepo-cloud/viscaufs works
Project type and purpose
• This is a distributed filesystem project (“ViscauFS”) that consists of:
• A FUSE-based client (“filesystem/…”) that mounts a remote, lazily-loaded container image
• A gRPC server (“server/…”) that downloads, indexes, caches, and serves image layer files
• A shared library (“common/…”) providing Adaptive Radix Tree indexing, protobuf definitions, util functions
File structure
• Top-level directories:
• common — fsindex library, humanization, and protobuf definitions
• filesystem — FUSE client implementation and example scripts
• server — monolithic gRPC server, internal services, database migrations, Docker/image test cases
• Config and build artifacts:
• go.mod/go.sum in each module, buf.yaml in common/proto
• server/db/migrations for SQLite schema, scripts under server/script & filesystem/script
• Architectural patterns:
• client/server over gRPC
• server built with Fx dependency injection (“server/internal/fxutil”)
• layered “service” packages inside the server (filehandlerservice, fsindexservice, imgservice)
README for additional insights
• Pipeline overview: download layers → index each layer (Adaptive Radix Tree) → merge indexes → serve file reads on first access
• Caching: layer indexes persisted to SQLite, reused across images