You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: 4 OSS contributions (not 1), correct status = open (not merged), README refresh
Ground truth via GitHub API: Stéphane shipped 4 contributions on 2026-04-22,
all currently 'open' / awaiting review (none merged yet). Previous /contributions
page only listed 1 and claimed 'merged' — both wrong.
Changes:
- /contributions (EN+FR): now lists the 4 real contributions
· ublue-os/homebrew-experimental-tap#309 (PR, claude-code-linux cask) — first of the day
· requarks/wiki#7986 (discussion, render IS NULL bug report)
· grafana/alloy#6108 (PR, Promtail docs migration guide)
· wazuh/wazuh-documentation#9512 (PR, warn about wazuh-agent postinst)
- Status field: 'merged' → 'open' (honest; none merged upstream yet)
- 'merged' date field → 'shipped' field semantically (day submitted)
- /making-of/v3: 'first OSS PR accepted' → 'four OSS contributions shipped in one day'
- Homepage OSS brick (EN+FR): contextualized PR #309 as 'first of four that day'
- README.md: full refresh — 55 services (was 36), 4 PVE (was 3), 13 pages (was 8),
SessionImprint, TopologyMap, DynNum, data pipelines documented
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+56-16Lines changed: 56 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
# pixelium.win
2
2
3
-
Bilingual portfolio (EN/FR) built with Astro and deployed on Cloudflare Workers.
4
-
Live dashboard monitoring 36 self-hosted services across a 3-node Proxmox homelab.
3
+
Bilingual portfolio (EN/FR) written in the first person by Claude (an AI), reviewed and shipped by Stéphane (the human).
4
+
Built with Astro 6, deployed on Cloudflare Workers. Live dashboard monitoring **55+ self-hosted services** across a **4-node Proxmox** homelab, with **tri-state status** (up · on-demand · down) and **per-page SessionImprint** (each page signs itself with its own commit SHA).
Reads best after: [`/pact`](https://pixelium.win/pact) (the deal), [`/ia`](https://pixelium.win/ia) (the lab), [`/claude`](https://pixelium.win/claude) (the stats), [`/contributions`](https://pixelium.win/contributions) (the OSS ledger).
9
+
8
10
## Stack
9
11
10
12
| Layer | Technology |
@@ -16,40 +18,78 @@ Live dashboard monitoring 36 self-hosted services across a 3-node Proxmox homela
insight: 'The official Anthropic GCS /stable file lags up to 13 versions behind the npm registry. A livecheck pointing at npm catches releases the same day they ship.',
15
+
shipped: '2026-04-22',
16
+
status: 'open',
17
+
insight: "The official Anthropic GCS /stable file lags up to 13 versions behind the npm registry. A livecheck pointing at npm catches releases the same day they ship.",
insight: "Hit in production after a migration: pages with a NULL render column returned HTTP 500 instead of falling back to re-rendering from the source. Minimal repro + root cause pointer to server/models/pages.js#L952-L969 + suggested fix.",
31
+
tags: ['wikijs', 'postgres', 'bug-report'],
32
+
},
33
+
{
34
+
project: 'grafana / alloy',
35
+
title: 'docs: systemd journal example for Promtail → Alloy migration',
36
+
pr: 'https://github.com/grafana/alloy/pull/6108',
37
+
prNumber: 6108,
38
+
shipped: '2026-04-22',
39
+
status: 'open',
40
+
insight: "The official migration guide only covered file-based scrape configs, skipping the most common Linux source — systemd journal. Added a working example taken from a real production migration on 49 Debian hosts.",
insight: "The wazuh-agent package silently uninstalls wazuh-manager via dpkg Conflicts/Replaces when both are installed on the same machine. No warning in the install doc. Cost us a 17-hour silent outage (see /ia What I broke).",
insight: "Le fichier GCS /stable officiel d'Anthropic accuse jusqu'à 13 versions de retard sur le registre npm. Un livecheck qui pointe npm attrape les releases le jour même de leur publication.",
insight: "Rencontré en prod après migration : les pages dont la colonne render était NULL retournaient HTTP 500 au lieu de retomber sur un re-rendu depuis la source. Repro minimal + pointeur vers server/models/pages.js#L952-L969 + fix proposé.",
28
+
tags: ['wikijs', 'postgres', 'bug-report'],
29
+
},
30
+
{
31
+
project: 'grafana / alloy',
32
+
title: 'docs : exemple systemd journal pour la migration Promtail → Alloy',
33
+
pr: 'https://github.com/grafana/alloy/pull/6108',
34
+
prNumber: 6108,
35
+
shipped: '2026-04-22',
36
+
status: 'open',
37
+
insight: "Le guide de migration officiel ne couvrait que les configs scrape file-based, oubliant la source Linux la plus courante — le journal systemd. Ajout d'un exemple fonctionnel tiré d'une vraie migration prod sur 49 hosts Debian.",
insight: "Le paquet wazuh-agent désinstalle silencieusement wazuh-manager via dpkg Conflicts/Replaces quand les deux sont installés sur la même machine. Aucun avertissement dans la doc install. Nous a coûté 17h de panne silencieuse (voir /ia What I broke).",
0 commit comments