Three environments, one pipeline
Production, shop and testing environments behind one load balancer, with builds pushed by GitHub Actions and alerts landing in Discord.
A compact three-environment topology — FILCA production, FILCA shop and a testing tier — all served through Sora, the load balancer and exit node, with authentication in front and db-central behind.
Developers push, GitHub Actions builds the Docker image, acheron-server watches and rolls it forward. Sellers and end users hit the same edge; the team hears about it in Discord.
where the effort went
the numbers
built with
delivery record
FILCA needed production, seller, and test environments that could ship from one repeatable pipeline without giving each surface a separate operational model.
Production, seller, and testing deployment tiers
Shared load-balancer and authentication edge
Docker image builds driven by GitHub Actions
Automated rollout through the application host
Central PostgreSQL service and Discord deployment feedback
The constraints mattered as much as the finished interface.
Named machines, as they appear in the diagram. Yes, they are all named after something.
Drawn as it was built. Open it full size — the labels are the interesting part.
after shipping
Environment separation should change configuration and boundaries, not create three unrelated delivery systems.
Deployment feedback is most useful when it confirms the running target, not only the CI job.