From 01808882b13a583bae8d577e201cf807c7e0c8b5 Mon Sep 17 00:00:00 2001 From: devin Date: Tue, 14 Jul 2026 13:08:09 -0400 Subject: [PATCH] Update deployment instructions in DEPLOYING.md Clarified deployment instructions and added notes on DB migrations. --- DEPLOYING.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/DEPLOYING.md b/DEPLOYING.md index 91db67f..4bb588a 100644 --- a/DEPLOYING.md +++ b/DEPLOYING.md @@ -135,23 +135,28 @@ Nothing manual to do here. The object is created manually. just dev ``` -**Deploy all workers:** +**Deploy or upgrade all workers:** 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 account (`wrangler login`, or `CLOUDFLARE_API_TOKEN` / `CLOUDFLARE_ACCOUNT_ID` in the environment). 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 -just deploy # for all services -just deploy -F rooms # for a single microservice +just install # Makes sure dependencies are up to date +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 - `apps/` - The service workers, one deployable Worker per subdirectory. Each has