New monorepo, Docker comparison, and journal catch-up
Scaffolded an oRPC + Hono monorepo, compared it side-by-side with the legacy system in Docker, and updated the journal.
A productive scaffolding day. A project took shape as a real monorepo, with API, frontend, and dev pipeline all configured.
oRPC + Hono monorepo
The main work was setting up a new monorepo. I chose oRPC for end-to-end type safety and Hono as a lightweight HTTP server. I configured reference skills (advanced TypeScript, Hono best practices, oRPC fullstack) to keep code quality high from the start.
On the frontend, I defined the stack: shadcn UI, React Hook Form, Zod for validation, and custom hooks to separate logic from UI. Two PRs were merged with the full API and Next.js scaffold.
Legacy vs. new comparison
To validate the migration, I ran both projects (legacy and new) in Docker side by side on different ports. This let me visually compare behavior and confirm the new structure reproduces what the old system does.
Daily journal
I also caught up on the site's delayed journal entries and opened a PR with the new ones.
The takeaway: a solid scaffold at the start saves weeks of rework later.