deployment-and-devops
/deployment-and-devops
Prowadzi CI/CD i hosting platformy: pipeline w GitHub Actions, usługi Render, konfigurację Vercel, rozdział środowisk Supabase i bramki migracji.
- Autor
- arcange-dev ↗
- Repozytorium
- veritas-bot ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Prowadzi CI/CD i hosting platformy: pipeline w GitHub Actions, usługi Render, konfigurację Vercel, rozdział środowisk Supabase i bramki migracji.
Oryginalny opis (EN)
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.
Jak działa
- When to use
- Environments
- Pipeline
- Render services
- Frontend on Vercel
- Rollback
- Observability
- Checklist
Podgląd SKILL.md
---
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.
Wersje
W bazie nie ma innych skilli o nazwie deployment-and-devops.
Migawka bazy z 13.11.2026 · wersja paczki 41c4e6080e38 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90vercel-deployment
Wdraża aplikacje Next.js na Vercel, obejmując deployment, hosting i środowisko produkcyjne. - 90vercel-deployment
Wdraża aplikacje Next.js na Vercel, obejmując deployment, hosting i środowisko produkcyjne. - 100release
Przygotowuje konfigurację wdrożenia lokalnie dla Render lub Vercel i sprawdza build, start, zmienne i health check bez wdrażania. - 95deployment-cicd
Opisuje wdrażanie aplikacji przez pipeline'y CI/CD, konteneryzację i infrastrukturę jako kod z GitHub Actions, Dockerem, Vercel i wzorcami chmurowymi. - 90devops-engineer
Projektuje potoki CI/CD, wdrożenia, infrastrukturę, monitoring i reagowanie na incydenty, w tym GitHub Actions, Docker i hosting w chmurze. - 100web-deploy
Wdraża aplikację webową na Vercel lub Render i czyta oraz zapisuje zmienne środowiskowe przez API i GitHub Actions.