Hello,
This update covers two weeks of MapCTF development as part of the effort to catch the series up to the current state of the project. Grouping this work into a single post gives a clearer view of how the platform kept evolving across multiple areas at once, from backend behavior and admin tooling to the overall operational experience.
Let’s go!
Week of February 9, 2026
Docker works, UUIDs win, and the map service appears
Infrastructure hardening and future-proofing.
The big milestone this week was infrastructure hardening. The Docker dev environment became functional, the API gained CORS for frontend integration, and a dedicated map service was introduced to serve templates and map-facing UX.
What landed
Functional Docker development environment
CORS support in the API
Dedicated map service
UUID refactor across services and packages
Why it matters
Under the hood, the codebase moved away from older identifier assumptions and refactored hard toward UUIDs across packages and services. That is not glamorous work, but it is the kind of change that prevents future archaeology. We also refreshed the sample config and pulled dependency updates for Redis and crypto primitives.
Referenced commits
Week of February 16, 2026
The UI landed with actual HTML, not just optimism
The project started becoming visible to users.
MapCTF’s map-facing interface arrived in force this week. The repository gained the template set for the UI, then quickly followed with a functional HTML-based map service and the required map UUID wiring.
What landed
Full template set for the UI
Functional HTML-based map service
Map UUID wiring
Why it matters
This is the point where the platform started to look like software users can touch. The server now serves more than JSON and ambition; it serves pages, templates, and the beginning of a coherent gameplay surface.
Referenced commits
See you next week!
Follow along
Telegram channel: t.me/mapctf
Best regards,
MapCTF Development Updates