Update deployment instructions in DEPLOYING.md

Clarified deployment instructions and added notes on DB migrations.
This commit is contained in:
devin
2026-07-14 13:08:09 -04:00
committed by GitHub
parent 505243844c
commit 01808882b1
+9 -4
View File
@@ -135,23 +135,28 @@ Nothing manual to do here. The object is created manually.
just dev just dev
``` ```
**Deploy all workers:** **Deploy or upgrade all workers:**
This will deploy all workers to respective endpoints (*.example.com) This will deploy all workers to respective endpoints (*.example.com)
It will additionally run any necessary DB migrations.
Deploying requires `wrangler` to be authenticated against your Cloudflare Deploying requires `wrangler` to be authenticated against your Cloudflare
account (`wrangler login`, or `CLOUDFLARE_API_TOKEN` / `CLOUDFLARE_ACCOUNT_ID` account (`wrangler login`, or `CLOUDFLARE_API_TOKEN` / `CLOUDFLARE_ACCOUNT_ID`
in the environment). in the environment).
It requires the storage to be set up above, otherwise, deployments may fail. It requires the storage to be set up above, otherwise, deployments may fail.
You can always re-run it as often as you wish. You can always re-run it as often as you wish. DB migrations will only run once.
```bash ```bash
just deploy # for all services just install # Makes sure dependencies are up to date
just deploy -F rooms # for a single microservice just migrate # Runs DB migrations
just deploy # Deploy code
``` ```
Optionally if you know there was only a change to a single service, you can use `just [migrate|deploy] -F econ` for example to only deploy the `econ` microservice.
## Repository Structure ## Repository Structure
- `apps/` - The service workers, one deployable Worker per subdirectory. Each has - `apps/` - The service workers, one deployable Worker per subdirectory. Each has