How kaushalrijal/veloce works
Project type and purpose
• Veloce is a command‑line version control system (VCS) written in C.
• Purpose: let users authenticate, create/manage repositories, record commits, view history, and revert changes.
File structure
• Top‑level C modules:
• main.c → CLI orchestration and menu flow
• auth.c → user signup/login, password encryption, security questions
• repos.c → create/list/delete repositories
• commits.c → create commits, list commit history, revert to an earlier state
• loading.c → persistence: reading/writing .dat files for users, repos, commits
• vcs.h → shared data structures and function prototypes
• No external services or databases—persistence is file‑based.
README for additional insights
• Features map one‑to‑one with modules above.
• Build instructions show standalone GCC compilation into a single vcs executable.
Elements
• Clear labels: module names and their source files
• CLI → Auth (login/signup) → Persistence
• CLI → Repo → Persistence
• CLI → Commit → Persistence
• Blue rectangles for “Services” (Auth, Repo, Commit)
• Yellow oval for “CLI Interface”
• Grey rectangle for “Loading / Data Access Layer”
Detailed breakdown
• Split each service into input (functions called by main.c) and output (files read/written)
• “revert” flow: Commit Service reads commit object, writes new HEAD pointer in the repo file
3. Loading module connecting to “File System (.dat files)”
This layered, modular view ensures all components and their interactions are captured accurately and in detail.