deployment-and-devops
/deployment-and-devops
CI/CD and hosting for the platform - GitHub Actions pipeline shape, Render services and health checks, Vercel frontend config, Supabase environment separation, migration gating, rollback, and observability. Use when changing CI, infrastructure, environment config, or a release procedure.
- Author
- arcange-dev ↗
- Repository
- veritas-bot ↗
- Licence
- Apache-2.0
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
CI/CD and hosting for the platform - GitHub Actions pipeline shape, Render services and health checks, Vercel frontend config, Supabase environment separation, migration gating, rollback, and observability. Use when changing CI, infrastructure, environment config, or a release procedure.
Original author description
CI/CD and hosting for the platform - GitHub Actions pipeline shape, Render services and health checks, Vercel frontend config, Supabase environment separation, migration gating, rollback, and observability. Use when changing CI, infrastructure, environment config, or a release procedure.
How it works
- When to use
- Environments
- Pipeline
- Render services
- Frontend on Vercel
- Rollback
- Observability
- Checklist
SKILL.md preview
---
name: deployment-and-devops
description: CI/CD and hosting for the platform - GitHub Actions pipeline shape, Render services and health checks, Vercel frontend config, Supabase environment separation, migration gating, rollback, and observability. Use when changing CI, infrastructure, environment config, or a release procedure.
---
# Deployment and DevOps
## When to use
Editing `.github/workflows`, `infrastructure/**`, Render/Vercel config, environment
matrices, or running a release.
## Environments
| Env | Frontend | API | DB | Purpose |
|---|---|---|---|---|
| local | Vite dev | runserver | docker postgres | development |
| preview | Vercel preview | Render PR service (optional) | Supabase branch | per-PR review |
| staging | Vercel | Render | separate Supabase project | migration rehearsal |
| production | Vercel | Render | dedicated Supabase project | live |
Separate Supabase projects, separate secrets, separate GitHub App installations. Nothing is
shared between staging and production except code.
## Pipeline
```yaml
# .github/workflows/ci.yml (shape, not a copy-paste template)
jobs:
api:
services: { postgres: { image: postgres:16, env: {...} }, redis: {...} }
steps: [checkout, setup-python, pip-install, ruff, mypy, manage.py check,
makemigrations --check --dry-run, migrate, pytest --cov, bandit, pip-audit]
web:
steps: [checkout, setup-node, npm ci, typecheck, vitest run, build, playwright]
runner:
steps: [checkout, setup-python, pip-install -e ., pytest]
```
`makemigrations --check --dry-run` in CI is mandatory: a model change without a migration
fails the build. Migrations run as a separate release step, never inside a web container
start command that could run 3 times concurrently.
## Render services
- `api-web`: gunicorn/uvicorn workers, `preDeployCommand: python manage.py migrate`,
health check `/healthz` (checks DB + Redis, 2s timeout, returns 503 on failure).
- `api-worker`: `celery -A config worker -Q agents,execution,default`, concurrency tuned to
memory, `--max-tasks-per-child=50` to bound leaks.
- `api-beat`: single instance only.
- Auto-deploy from `main` after CI passes; no deploy from a branch.
## Frontend on Vercel
- `VITE_API_BASE_URL` per environment; no secret in any `VITE_*` variable.
- SPA rewrites to `index.html`, immutable caching for hashed assets, no caching for
`index.html`.
- Build fails if `typecheck` fails.
## Rollback
1. Revert the deploy (Render rollback / Vercel instant rollback).
2. Migrations: forward-only by default. If a bad migration shipped, ship a corrective
migration; do not edit history. Data-destructive changes always have a documented
rollback plan before merge.
3. Feature flags for anything risky so rollback is a flag flip, not a redeploy.
## Observability
- Structured JSON logs with `request_id`, `org_id`, `run_id`, `step_id`; secrets redacted.
- Sentry for exceptions on web/worker/frontend, with `beforeSend` scrubbing.
- Metrics that matter: run success rate, p50/p95 step latency, provider error rate per
provider, sandbox provisioning failures, queue depth, spend per org vs cap.
- Alerts: error rate > 2% for 5 min, queue depth > 500, provider 401 spike (credential
problem), sandbox orphan count > 0 after the reaper.
## Checklist
- [ ] CI green including migration check and both test suites.
- [ ] Health check returns real dependency status.
- [ ] New env var added to `.env.example`, Render, Vercel, and the docs table.
- [ ] Migration gated as a pre-deploy step.
- [ ] Rollback path written for anything destructive.
- [ ] No secret in a build-time variable.
Versions
The database has no other skills named deployment-and-devops.
Database snapshot: 13.11.2026 · package version 41c4e6080e38 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90vercel-deployment
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production. - 90vercel-deployment
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production. - 100release
Prepare local Render or Vercel deployment configuration and verify build, start, output, environment, and health-check readiness without deploying. Use for /release, Render setup, Vercel setup, deploy readiness, render.yaml, or vercel.json. - 95deployment-cicd
Deploy applications with confidence using CI/CD pipelines, containerization, and infrastructure as code. Covers GitHub Actions, Docker, Vercel, and cloud deployment patterns. Triggers on deployment, CI/CD, Docker, GitHub Actions, or DevOps requests. - 90devops-engineer
Designs CI/CD pipelines, deployment, infrastructure, monitoring and incident response. Use for setting up deployments, GitHub Actions, Docker, cloud hosting, uptime monitoring or reducing infrastructure cost. - 100web-deploy
Deploy a web app to Vercel or Render and read/write its deployment env vars through APIs and GitHub Actions instead of clicking a dashboard. Covers the one-token Vercel + GitHub Actions setup (org-level secrets, per-repo project id, turning off Vercel's native Git auto-deploy),…