2025 · Team · Archived
Aniclo
A full-stack application architected and shipped end to end for the PK Fokam research centre.
Mission
Aniclo is the application I built at the PK Fokam Institute research centre: architected backend and frontend, implemented the core features, and owned the release process from first commit to market launch.
For whom: the institute and its users. Constraints: a research-centre timeline, two people, and a release process I had to define before I could follow it.
Manifest
| Layer | Choice | Version | Why |
|---|---|---|---|
| services | Node.js backend | — | Published as its own image. |
| app | React frontend | — | Published as its own image. |
| data | PostgreSQL | — | Relational data with migrations. |
| infra | Docker Hub images | — | Deployable by the centre without access to my machine. |
Decisions
Backend and frontend as separate images. Published to Docker Hub so the centre could deploy without my laptop.
One release process, written down. Tags, images, and a rollback path before the first launch.
Impact
- Backend image pulls
- 1,094
- Frontend image pulls
- 902
Live at anilco.net; 1,094 backend and 902 frontend image pulls on Docker Hub.
What broke
The first thing I would fix: the two images were versioned independently, so a frontend could be deployed against a backend with a different API shape. Pinning the pair in one release manifest is the change I would make first.
Ship log
- Started
- Launched and handed over