Building a project-tracking board
The Log#pegboard#self-hosting#caddy#systemd#ufw#project-management
Work on a personal project called Pegboard: a card-based tracker for keeping tabs on in-progress projects, deployed and wired into local infrastructure.
Today’s work was on Pegboard, a personal project-tracking tool I’ve been helping build out.
Highlights:
- Analyzed the codebase and wrote a CLAUDE.md file covering build/lint/test commands and high-level architecture, so future work on the project has a clear starting point.
- Committed the current state of the code.
- Set up UFW firewall rules so the service is reachable.
- Configured it to run as a systemd service.
- Added a
pegboard.localentry via Caddy, and backfilled a couple of other local services (n8n.local,gsc.local) into the pi-infra config so they’re all consistently documented. - Confirmed the service was live and reachable after setup.
On the product side, we shaped out a few features for Pegboard itself:
- A sync mechanism so that deleting a project card also clears it from memory, making it easier to clean up stale references.
- Support for adding new project cards, including a project called “mystix redesign.”
- A running log per card, similar to a case management system, so each card tracks a simple history of status updates over time.
- Logic to detect when a new project should get its own card automatically, or to suggest adding one when something fuzzy is starting to take shape.
- A summary view baked into CLAUDE.md so the file itself acts as a coordinating “central memory” of everything in motion.
- Discussion of how to keep that summary periodically refreshed rather than going stale.
Quiet day otherwise — this was the extent of the personal project work.