How mrdionesalvi/sistemi-operativi works
Project type and purpose
• This is a monorepo for an academic operating-systems course containing:
a. “Laboratorio” folder: C-language lab exercises (Lab02–Lab09).
b. “Teoria” folder: LaTeX source for course theory chapters and compiled PDF.
c. README with WakaTime badge, .vscode configs, .gitignore, LICENSE.
• It’s not a classical client-server app but a combined documentation + code-sample project with a build pipeline and dev-tool integrations.
File structure
• Top level:
• .gitignore, .vscode/, LICENSE, README.md (repo metadata/config)
• Laboratorio/ (all C exercises grouped by lab)
• Teoria/ (LaTeX source, images, environment styles, final main.pdf)
• Each lab directory: C source, supporting PDFs, test files, subfolders (e.g., server-client).
• Teoria has chapters, enviroment (sty files), images, and final outputs.
• No formal build scripts (Makefile) present, but implicit build steps: gcc for C code, pdflatex for docs.
• External integration: WakaTime badge in README (metrics service).
README for additional insights
• It only exposes a WakaTime project badge—implying developer metric tracking.
• No further architecture or tech-stack explanation.
a. Main components
1. Version Control: Git Repo (GitHub/GitLab)
2. Developer Workstation + IDE (with .vscode settings & WakaTime plugin)
3. “Laboratorio” module (C code for Labs)
4. “Teoria” module (LaTeX source → main.pdf)
5. Build Tools:
• GCC toolchain (compile & run C labs)
• pdflatex (build PDF from Teoria)
6. Outputs: Executable binaries (lab tests), main.pdf
7. External Service: WakaTime analytics
b. Relationships & interactions
• Developer pulls/clones repo → edits code or LaTeX → invokes build tools → generates executables or PDF → runs/tests C code.
• IDE usage: reads/writes source, uses .vscode to configure linters, and pushes time metrics to WakaTime.
• Version Control: commit/push changes back to remote.
• README displays WakaTime badge (fetched from WakaTime API).
c. Architectural patterns/principles
• Monorepo structure separating code and documentation.
• Convention-over-configuration: directory naming by lab number.
• Toolchain decoupling: C compile pipeline vs. LaTeX build pipeline run independently.
d. Key technologies/frameworks/libraries
• C language, GCC compiler
• LaTeX, pdflatex, custom .sty environment files
• WakaTime plugin & badge API
• Git, .vscode for IDE configuration
Elements
• Clear labels for each component (e.g., “Laboratorio (C Labs)”, “Teoria (LaTeX)”)
• From Git Repo to Developer IDE
• IDE → Build Tools → Outputs
• IDE → WakaTime Service → README Badge
Final Recommendations
• Be exhaustive: break down each Lab (e.g., Lab05 server-client submodule) if further detail is needed.
• Paths: source → build → test/report.