Why Obsidian? When building an AI infrastructure from scratch — Proxmox, GPU passthrough, local LLMs, RAG, Python pipelines — memory is no longer enough. I needed a tool that stores my notes locally, in pure Markdown, with no cloud subscription, and that links concepts together. Obsidian has been the building companion for this entire infrastructure: every command tested, every error encountered, every architecture decision has been logged in a dedicated vault. This portfolio is, in part, the public synthesis of it.
Overview

Obsidian is a local-first Markdown note editor: files stay on disk, in plain text format. No account required, no data sent to the cloud by default. Its strength lies in the bidirectional link graph ([[wikilink]]) that turns isolated notes into a navigable knowledge network.

  • Markdown files stored locally (C:\Notes\infra-vault)
  • Interactive graph of links between concepts
  • Instant full-text search across the whole vault
  • Templates to standardize note-taking
  • Community plugins (Dataview, Kanban, Calendar…)
  • Optional sync via OneDrive or Git
Why this choice?
CriterionDecision
Data sovereigntyLocal files, zero cloud dependency
Long-lasting formatMarkdown — readable without Obsidian in 10 years
No subscriptionFree for personal use (Sync and Publish optional)
SpeedLaunches in < 1 s, real-time search
Bidirectional linksNaturally link Proxmox ↔ GPU ↔ LLM ↔ Docker
ExtensibleDataview plugin = SQL-like queries on notes
Concrete role in building the infrastructure

The infra-vault vault has accompanied every stage of the project, from the technology watch phase to the writing of this portfolio. Here are the uses that really made a difference:

📋 Build journal

One note per work session: goal, commands tested, errors encountered, solution adopted. Essential for resuming a task after several days off without losing context.

markdown — illustrative example of a session note (does not describe the current platform)
## 2024-11-14 — GPU Passthrough VFIO
**Objectif :** Isoler la RTX 3090 pour la VM LLM

### Commandes testées
```bash
lspci -nn | grep NVIDIA
# 0000:01:00.0 [10de:2204]
```
### Problème rencontré
IOMMU group partagé → ajouter pcie_acs_override=downstream

### Solution
Kernel param : `intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction`

→ [[gpu_passthrough]] pour la doc finale

🗺️ Architecture mind map

Every infrastructure component has its own dedicated note, linked via wikilinks. The Obsidian graph visualizes dependencies in real time: Proxmox → LLM VM → Docker → Ollama → Open WebUI.

📚 Technology watch base

Articles, model benchmarks, comparisons (LLaMA vs Mistral vs Phi), reading notes on RAG and Qdrant. All centralized, retrievable in 3 seconds via full-text search.

Vault graph view

Obsidian's graph view visually connects notes: each dot is a note, each line a link. It reveals thematic clusters (infrastructure, AI, DevOps…) and the vault's central notes.

Vue graphe du vault Obsidian — plus de 200 notes reliées, organisées en grappes thématiques colorées par dossier
Knowledge graph — 200+ linked notes, colored by folder.
Vault structure infra-vault
tree — Obsidian vault dedicated to the infrastructure
infra-vault/
├── 00-inbox/               ← Notes brutes, à trier
│   └── 2026-06-16.md
├── 01-journal/             ← Une note par session de travail
│   ├── 2024-11-14-gpu-passthrough.md
│   └── 2025-03-08-rag-qdrant.md
├── 02-infrastructure/      ← Documentation technique
│   ├── proxmox.md
│   ├── zfs-storage.md
│   ├── gpu-passthrough.md
│   └── reseau.md
├── 03-ia/                  ← IA & modèles
│   ├── llm-comparatifs.md
│   ├── ollama-setup.md
│   ├── rag-architecture.md
│   └── comfyui.md
├── 04-devops/              ← Outils & workflows
│   ├── docker-compose.md
│   ├── git-strategie.md
│   └── python-scripts.md
├── 05-veille/              ← Articles, benchmarks, liens
│   └── modeles-llm-2025.md
├── 06-portfolio/           ← Brouillons des pages web
│   └── obsidian-page.md    ← (cette page est née ici)
└── templates/
    ├── session.md
    └── tech-fiche.md
Golden rule: every technical note in 02-infrastructure/ or 03-ia/ ends with a ## References section listing the URLs consulted — exactly like the pages of this portfolio.
Essential plugins
PluginConcrete use
DataviewQueries on notes — list of all open tasks
TemplaterSession templates with auto date and contextual links
CalendarDate-based navigation in the build journal
GitAutomatic vault commit every 30 min
KanbanTracking board for infra tasks in progress / done
ExcalidrawArchitecture diagrams directly in the notes
🎯 Skills demonstrated
  • Organizing a vault by domain (adapted PARA)
  • Writing Dataview queries for dashboards
  • Creating Templater templates with dynamic variables
  • Automatic Git sync of the vault
  • Link between the Obsidian vault and the portfolio GitHub repository
  • Navigable knowledge graph (200+ linked notes)
  • Using Obsidian Publish for selective sharing
Intermediate
Example — Dataview query

Dataview lets you query the vault like a database. Example: display all in-progress infra tasks, sorted by last modification date.

dataview — open-tasks dashboard
```dataview
TABLE
  file.mtime AS "Dernière modif",
  status AS "Statut",
  tags AS "Tags"
FROM "02-infrastructure" OR "03-ia"
WHERE status = "en-cours"
SORT file.mtime DESC
```
Result: a table automatically updated every time the vault is opened — no manual entry. Same principle as a project view in a tool like Notion, but entirely local and in plain Markdown.
From the Obsidian vault to this portfolio

This portfolio was not written from scratch. Each HTML page is the publishable version of an existing Obsidian note, enriched and formatted. The workflow is simple:

📝
1. Session note
Raw note-taking during the build
↓
🗂️
2. Technical sheet
Consolidation into 02-infrastructure/ or 03-ia/
↓
📄
3. Portfolio draft
Writing in 06-portfolio/
↓
🌐
4. Published HTML page
portfolio.stephanemuraro.fr

Key advantage: the Obsidian note remains the source of truth. If a config changes (Proxmox version, updated LLM model), the note is updated first, then the HTML page is synced.

This flow also keeps unpublished information in the vault (API keys, internal IP addresses, sensitive debug notes) with no risk of exposing it on GitHub.

The vault itself is versioned on a private GitHub repository, separate from the portfolio's public repository.

Level of mastery
FeatureLevelNotes
Daily Markdown note-takingAdvancedDaily use since 2024
Bidirectional links & graphAdvanced200+ interconnected notes
Templater — dynamic templatesIntermediateSession templates and technical sheets
Dataview — queriesIntermediateDashboards, filtered lists
Automatic Git syncIntermediateObsidian Git plugin — commit every 30 min
Excalidraw — embedded diagramsBasic+Simple architecture diagrams

References & Sources

CategoryResourceURL
Official site Obsidian — The private and flexible writing app obsidian.md
Official documentation Obsidian Help — Getting started help.obsidian.md
Plugin Dataview — Query your vault github.com/blacksmithgu/obsidian-dataview
Plugin Obsidian Git — Vault versioning github.com/denolehov/obsidian-git
Plugin Templater — Dynamic templates github.com/SilentVoid13/Templater
Method PARA Method — Tiago Forte fortelabs.com/blog/para
Version used Obsidian v1.7.x — usage personnel (gratuit) —
License Propriétaire — gratuit pour usage personnel non commercial obsidian.md/license
Content of this page Shared under CC BY-SA 4.0 creativecommons.org/licenses/by-sa/4.0