TheSunIsLeaking/recflare
3
0
Fork 0
mirror of https://github.com/djdevin/recflare.git synced 2026-09-08 06:31:27 -07:00
Code Issues Packages Projects Releases Wiki Activity

Update deployment instructions in DEPLOYING.md

Browse Source 
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
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DEPLOYING.md
+9 -4
View File
@@ -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