You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository has several deployable services, but they do not all share one
4
+
deployment mechanism. The table below records the automation that exists in the
5
+
repository today so a successful CI build is not mistaken for a production
6
+
deployment.
7
+
8
+
| Service | Deployment path | Repository automation |
9
+
| --- | --- | --- |
10
+
| Backend | Railway deploy hook |`.github/workflows/deploy-backend.yml` runs only after the `CI` workflow succeeds for a push to `master`. A missing `RAILWAY_DEPLOY_HOOK_URL` fails the deployment instead of silently skipping it. |
11
+
| Client | Vercel Git integration |`client/vercel.json` controls Vercel build behavior and routing. There is no client deployment job in GitHub Actions. |
12
+
| Indexer | Kubernetes overlay |`indexer/k8s/` can be applied manually as described in [`k8s-deployment.md`](./k8s-deployment.md). There is no automated GitHub Actions deployment. |
13
+
| Oracle | Kubernetes overlay |`oracle/k8s/` can be applied manually as described in [`k8s-deployment.md`](./k8s-deployment.md). There is no automated GitHub Actions deployment. |
14
+
| SDK docs | GitHub Pages |`.github/workflows/docs.yml` publishes documentation. It does not deploy an application service. |
15
+
16
+
## Backend deployment gate
17
+
18
+
The backend build, lint, unit tests, and OpenAPI validation run once in the
19
+
`backend` job of `.github/workflows/ci.yml`. The deployment workflow listens for
20
+
the completed CI run instead of repeating those checks. It invokes Railway only
21
+
when all of the following are true:
22
+
23
+
1. the triggering CI run concluded successfully;
24
+
2. the CI run was caused by a push, not a pull request;
25
+
3. the tested branch was `master`; and
26
+
4. the `RAILWAY_DEPLOY_HOOK_URL` repository secret is configured.
27
+
28
+
Pull-request CI therefore never deploys. A failed or cancelled CI run also
29
+
never deploys. Deployment failure is visible in the separate `Deploy Backend`
30
+
workflow rather than being reported as a successful no-op.
31
+
32
+
## Manual Kubernetes deployment
33
+
34
+
The backend also has a Kubernetes overlay under `backend/k8s/`. It is an
35
+
operator-driven alternative documented in [`k8s-deployment.md`](./k8s-deployment.md),
36
+
not part of the Railway GitHub Actions path. The indexer and oracle currently
37
+
have only these operator-driven Kubernetes paths; adding automated deployment
38
+
for them requires a separate workflow and explicit environment/secret policy.
0 commit comments