Legacy Docker-era reverse proxy repository for alfares.cz services.
Retired from active production routing. Public ingress is now handled by Traefik in Kubernetes, and service routing lives in per-service k8s/ingress.yaml resources.
Owner-confirmed retirement was revalidated on 2026-06-17:
SYSTEM.mdalready marks the service retired.kubectl get ingress -n statex-appsreports active Traefik-managed ingresses.- no running container or Kubernetes workload named
nginx-microserviceexists onalfares.
This repository is kept as a legacy archive for:
- historical Docker/nginx blue-green scripts;
- archived generated configs and service-registry data;
- historical route-registration logic and verification tooling;
- certbot and migration-era operational notes.
Those assets are not the active production ingress path anymore.
- Ingress controller: Traefik
- Routing source of truth: service-owned Kubernetes ingress manifests
- Public ingress namespace:
statex-appsingresses served by the Traefik controller
Use Kubernetes/Traefik checks for current routing status, for example:
kubectl get ingress -n statex-apps
kubectl get pods -A | grep traefik
curl -skI https://127.0.0.1 -H 'Host: auth.alfares.cz'- Do not treat
service-registry/*.jsonas production routing truth. - Do not treat
nginx/conf.d/as the active ingress configuration. - Do not run blue/green nginx deployment scripts as part of current production routing unless the platform is explicitly rolled back to the Docker-era proxy model.
| Topic | File |
|---|---|
| Historical blue/green deployment | docs/BLUE_GREEN_DEPLOYMENT.md |
| Historical troubleshooting | docs/BLUE_GREEN_TROUBLESHOOTING.md |
| Historical container/nginx sync | docs/CONTAINER_NGINX_SYNC.md |
| Historical API routes registration | docs/API_ROUTES_REGISTRATION.md |
| Historical multi-app routing | docs/MULTI_APP_API_ROUTING.md |
| Historical service registry | docs/SERVICE_REGISTRY.md |
| Historical service dependencies | docs/SERVICE_DEPENDENCIES.md |