How anyproto/any-sync-filenode works
Project type and purpose
• This is a Go-based microservice implementing a “file node” as part of the Any-Sync protocol.
• It provides an RPC interface for storing, retrieving, indexing, and deleting file data, backed by S3-compatible storage and Redis.
File structure
• Top-level entrypoints under cmd/ produce executables:
• filenode – main service
• store / store_dev – direct store utilities
• Core packages:
• config – configuration loading (YAML)
• filenode – RPC handler and orchestration
• index – metadata indexing (with protobufs, pub/sub, migration)
• store – storage adapters (S3, file-dev, mock)
• redisprovider – pub/sub via Redis
• deletelog – write-ahead log of deletions
• account – identity / access control stubs
• stat – usage metrics
• Testing and mocks live alongside each package.
• Deployment bits: etc/any-sync-filenode.yml, GitHub Actions workflows, Makefile.
README
• Specifies external dependencies: S3-compatible object storage and Redis.
• Describes CLI options, configuration.
Detailed capture of essential elements
• Your config loader as the entrypoint feeding parameters to all modules.
• Test and mock packages only if illustrating extensibility or testing structure.