Skip to main content

Architecture Overview

This page describes the full production architecture: how source code flows from a developer's machine to a live URL, and how alerts are fired when something goes wrong.


CI/CD Flow


Production Stack


Network Architecture

NetworkPurposeWho's on it
rcb_publicInternet-facing; Traefik routes heretraefik, backend, frontend, keycloak, ghost, grafana
rcb_internalIsolated; never exposed to internetpostgres, prometheus, alertmanager, loki, backend, keycloak, grafana
ghost_internalGhost-only isolationghost, ghost-db

Rule: PostgreSQL, Prometheus, Alertmanager, and Loki are never on rcb_public. They cannot be reached from the internet.


Authentication Flow


Image Tagging Convention

Every Docker image is tagged with the short Git SHA at the time of the push:

ghcr.io/ivelin1936/rcb-backend:sha-abc1234
ghcr.io/ivelin1936/rcb-backend:future ← branch tag (latest on future)
ghcr.io/ivelin1936/rcb-frontend:sha-abc1234
ghcr.io/ivelin1936/rcb-frontend:master

The SHA tag is used for rollback. The branch tag (future / master) is always the latest deployed image.


Repositories

RepoPurposeBranch
ivelin1936/Renault-Club-BulgariaSpring Boot BE, infra scripts, backlogfuture
ivelin1936/renault-club-bulgaria-feReact FEmaster
ivelin1936/rcb-docusaurusThis documentation sitemain