← Back to writing

DevForge - A Command Center for Everything You're Building

I was running 30+ projects across three directories. Half were active, a quarter were on the backburner, and the rest were done or archived. Keeping track in my head stopped working around project 15.

DevForge is the tool I built to fix this.

What It Does

Run it once:

node scan.js --serve

It scans your configured directories, finds every project, and builds a dashboard at localhost:3000 showing:

  • Project name and README description
  • Detected tech stack (React, Next.js, Expo, FastAPI, Express, etc.)
  • Git metadata - last commit, commit count, branch
  • Source file count
  • Your status - Focus / Active / Backburner / Done / Archived

Statuses persist to state.json. You set them once and they stick.

Zero Dependencies

Node.js only. No npm install. No package.json to maintain. Just clone and run.

This was a deliberate choice - a project dashboard that itself needs dependency management is self-defeating.

The CLI

node scan.js --serve              # Live dashboard on :3000
node scan.js                      # One-shot static HTML build
node scan.js --add ~/projects     # Add a scan directory
node scan.js --remove ~/projects  # Remove a directory
node scan.js --list               # Show configured directories

Multi-directory support means you can scan ~/projects, ~/clients, and ~/experiments in one view without mixing them into the same folder.

What I Actually Use It For

Every morning, I open DevForge and set one project to Focus. Everything else is context - I can see what’s active, what’s stalled, what I’ve finished. The act of choosing a Focus project each day is itself useful. It forces a decision that’s easy to avoid when everything is scattered across a file manager.