Today I wrote the first line of code for Unicorn Commander and watched it compile. That's the whole story.
I started with a scaffold Dockerfile, Dockerfile.api, docker-compose.yml, nginx configs, the React app shell (index.html, package.json, postcss.config.js), the deploy script, and README files across one repo. Sixty-seven hundred lines dropped in one shot, thirty-five files I'd been turning over my head for a while.
The second commit was almost nothing: a README bump on the other repo, also part of unicorncommander.ai. Not worth a paragraph.
Sixty-seven hundred lines dropped in one shot, thirty-five files I'd been turning over my head for a while.
The real work was picking the stack and getting the pieces to fit. Two Dockerfiles (one for the app front, one for the API), a docker-compose to tie them together, nginx to sit in front and reverse-proxy, a deploy.sh that automates the whole thing onto a box. Client-side React app. The architecture on paper was easy, the architecture on disk was a different question.
It shipped. The thing boots now.
That's a Monday. You can't rush the first compile, but you also can't afford to let it linger. I'd rather have a ugly thing that works than a perfect thing that doesn't exist.
Tomorrow's the real work: API routes, auth, the actual product. Now we've got a foundation to build on.
- Production-Unicorn-Commander-website4
- Unicorn-Commander-website4
- Unicorn-Commander-website-production2
- unicorncommander.ai2