How emagood/datavaultledger works
Project type and purpose
• This is a single‐repository, full‐stack user‐management application built in Godot Engine 4.3.
• It uses GDScript for both client (front‐client) and server (back-sever) logic.
• Networking is handled via ENet (Thot-p2p), plain TCP and WebSocket transports.
• It provides CRUD operations on user records, credential verification, in-memory caching, file‐based persistence and a change‐history log.
File structure
• Top level:
• back‐sever/ – server‐side scenes and scripts
• front-client/ – UI scenes for user interaction
• class/ – core domain scripts (User, UserSearcher, UserArrayManager, ChangeHistory, etc.)
• lib/ – third‐party or shared libraries (bit‐wise utilities, compression, ENet/TCP/WebSocket wrappers, NVR file editor, DB tooling)
• data files (users.dat, history.dat, private_key.rsa, public_key.rsa, etc.)
• project.godot & .godot/ – Godot project settings and caches
• Key patterns:
• MVC‐style separation (Scenes in front‐client/back‐sever are View layers; class/ contains Controllers/Models)
• Monolithic server application inside Godot using GDScript modules
• File-based “database” with custom block reader/writer, optional AES encryption and compression
README for additional insights
• Confirms feature set: create, modify, delete users, authentication guard, cache sub‐system, history logging.
• Lists main scripts: User, UserSearcher, UserArrayManager, ChangeHistory.
• Mentions ENet, TCP and WebSocket transports under the Thot-p2p umbrella.