How 84adam/arkfile works
Component Relationships
A. Primary Data Flows:
• Client → WASM Encryption → Server → B2 Storage
• Server → SQLite (metadata storage)
• Client → Server → B2 Storage → Client
• Server → SQLite (metadata retrieval)
• Client → JWT Auth → Server
External Services Integration
• Caddy Web Server (as reverse proxy)
• TLS termination point
• Connection to main server
Security Layers
• Red border: Client-side encryption zone
• Blue border: TLS protection zone
• Green border: Server-side security measures
Technical Details
Annotations for:
• WASM compilation process
• JWT token flow
• Encryption/decryption points
• Database schema reference
• API endpoints
Specific Implementation Notes
Callouts for:
• Environment variables configuration
• File size limitations
• Authentication mechanisms
• Error handling paths
Architectural Patterns
Highlight:
• Clean architecture boundaries
• Separation of concerns
• Security layers
• Stateless design
• Rectangles: Services and applications
• Hexagons: Security components
• Clouds: External services
• Using clear hierarchical layout
• Grouping related components
• Maintaining consistent spacing
• Adding brief explanatory notes