dzenda/os
1
0
Fork 0
Code Issues Pull requests 4 Projects Releases Packages Wiki Activity Actions

Deploy config for fit-os.dzenda.eu #26

Open
dzenda wants to merge 1 commit from deploy-fit-os into main
pull from: deploy-fit-os
merge into: dzenda:main
Conversation 0 Commits 1 Files changed 3 +43 -2
dzenda commented 2026-11-14 18:09:31 +01:00
Owner
Copy link

Production deployment config for https://fit-os.dzenda.eu.

  • wrangler.jsonc: new env.production with the Workers custom domain, the production D1 (fit-os, EEUR) and KV ids, and the rate limits (bindings aren't inherited by environments). The top level stays a placeholder, so local dev keeps its local database and self-hosters aren't pointed at our resources.
  • bun run deploy:fit = CLOUDFLARE_ENV=production vite build && wrangler deploy.
  • docs/self-hosting.md: how the project's own instance is deployed.

Already done from this branch:

  • wrangler d1 create fit-os, wrangler kv namespace create OAUTH_KV
  • wrangler d1 migrations apply fit-os --remote --env production (0000–0002)
  • deployed fit-os-production with a secrets file. TOKEN_ENCRYPTION_KEY and BETTER_AUTH_SECRET are freshly generated and kept in a git-ignored, owner-only .dev.vars.production.json, never committed. PUBLIC_URL is also set.

Remaining before sign-in works: the owner sets FIT_AUTH_CLIENT_ID / FIT_AUTH_CLIENT_SECRET (wrangler secret put … --env production) and registers https://fit-os.dzenda.eu/auth/callback on the FIT OAuth app.

Smoke test so far: TLS and security headers OK, OAuth protected-resource and authorization-server metadata OK (S256 PKCE, DCR endpoint), /mcp returns 401 without a token.

🤖 Generated with Claude Code

Production deployment config for **https://fit-os.dzenda.eu**. - `wrangler.jsonc`: new `env.production` with the Workers custom domain, the production D1 (`fit-os`, EEUR) and KV ids, and the rate limits (bindings aren't inherited by environments). The top level stays a placeholder, so local dev keeps its local database and self-hosters aren't pointed at our resources. - `bun run deploy:fit` = `CLOUDFLARE_ENV=production vite build && wrangler deploy`. - docs/self-hosting.md: how the project's own instance is deployed. Already done from this branch: - `wrangler d1 create fit-os`, `wrangler kv namespace create OAUTH_KV` - `wrangler d1 migrations apply fit-os --remote --env production` (0000–0002) - deployed `fit-os-production` with a secrets file. `TOKEN_ENCRYPTION_KEY` and `BETTER_AUTH_SECRET` are freshly generated and kept in a git-ignored, owner-only `.dev.vars.production.json`, never committed. `PUBLIC_URL` is also set. Remaining before sign-in works: the owner sets `FIT_AUTH_CLIENT_ID` / `FIT_AUTH_CLIENT_SECRET` (`wrangler secret put … --env production`) and registers `https://fit-os.dzenda.eu/auth/callback` on the FIT OAuth app. Smoke test so far: TLS and security headers OK, OAuth protected-resource and authorization-server metadata OK (S256 PKCE, DCR endpoint), `/mcp` returns 401 without a token. 🤖 Generated with [Claude Code](https://claude.com/claude-code) 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin deploy-fit-os:deploy-fit-os
git switch deploy-fit-os

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff deploy-fit-os
git switch deploy-fit-os
git rebase main
git switch main
git merge --ff-only deploy-fit-os
git switch deploy-fit-os
git rebase main
git switch main
git merge --no-ff deploy-fit-os
git switch main
git merge --squash deploy-fit-os
git switch main
git merge --ff-only deploy-fit-os
git switch main
git merge deploy-fit-os
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dzenda/os!26
No description provided.