We are shipping our first production release. v0.1.0 of the Autolux Bus Station frontend is tagged — an app for booking and buying intercity bus tickets, with a Next.js storefront and admin panel, a NestJS API, Postgres and Redis. This is how it gets to production, and what we deliberately did not use.

What "GitOps" means in this project

The repository is literally called gitops , and a reader would expect ArgoCD, Helm and a cluster. There is none. No Kubernetes, no container registry, no pull-based reconciliation.

What the gitops repo actually holds is a disaster-recovery workflow : a GitHub Action that, once a day,

clones every project repository (API, frontend, Android app, and itself) and tars them without .git ,

runs pg_dump against the production database,

restores that dump into a throwaway postgres:17 service container — the job fails if the restore fails,

uploads both files to Google Drive, mirrored into a second folder/account,

on success pings the QA topic in Telegram; on failure creates…