docs: record two-region Fly scaling (syd + iad)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
ccf0e6b0dc
commit
874374f03f
@@ -276,6 +276,15 @@ make deploy # flyctl deploy --remote-only
|
|||||||
`make deploy-status` shows machine and health-check state. The app serves
|
`make deploy-status` shows machine and health-check state. The app serves
|
||||||
the SPA at `https://<app>.fly.dev/` with `/api/health` as the health check.
|
the SPA at `https://<app>.fly.dev/` with `/api/health` as the health check.
|
||||||
|
|
||||||
|
Machine placement is imperative rather than part of `fly.toml`; the current
|
||||||
|
production topology is one machine in Sydney and one in Virginia:
|
||||||
|
|
||||||
|
```sh
|
||||||
|
flyctl scale count 2 --region syd,iad
|
||||||
|
```
|
||||||
|
|
||||||
|
`flyctl deploy` preserves existing machines and regions on redeploys.
|
||||||
|
|
||||||
### Continuous deployment
|
### Continuous deployment
|
||||||
|
|
||||||
`.gitea/workflows/deploy.yml` deploys on any `v*` tag push (or manual
|
`.gitea/workflows/deploy.yml` deploys on any `v*` tag push (or manual
|
||||||
|
|||||||
Reference in New Issue
Block a user