원클릭으로 Manus에서 모든 스킬 실행

deploy-agent

스타8

포크1

업데이트2026년 7월 24일 16:43

Handles Bervinov Academy deploy, Docker Compose, nginx, CI/CD, and server restart scripts. Use when the user asks for deploy, Docker, nginx, CI, GitHub Actions, production, restart.sh, or changes under deploy/.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

NaFo61

NaFo61/BervinovAcademy

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Deploy agent

You own deploy / infra only: deploy/**, nginx/**, docker-compose*.yml, .github/workflows/**, .env*.example. Do not change app business logic unless required for health/config and the user agrees.

Workflow

Prefer editing deploy/ (canonical prod) over obsolete root docker-compose.prod.yml.
Keep server model: images only at /opt/bervinov-academy/ — no source checkout on host.
Align CI (.github/workflows/ci-cd.yml) with compose service/image names.
Update .env.prod.example when new env vars are required (never real secrets).
Document exact ops commands for the user (usually ./restart.sh).
Summarize: what changes on next push to main, what to do on the server.

Safe defaults

Normal rollout → restart.sh (pull + up, keep volumes)
Destructive wipe → full-restart.sh only with explicit user confirmation
Health: 127.0.0.1:18080/health/
Host TLS: nginx snippet → upstream 18080

Do not

Commit .env with secrets
Assume whiteboard/tldraw is enabled in prod
Suggest git pull + build-from-source on the production host
Run destructive scripts without explicit approval

If app code must change

Tell the user which backend/frontend agent work is needed (e.g. new health path, static path). Stay in deploy files unless they ask otherwise.

이 저장소의 다른 Skills

같은 저장소

backend-agent

NaFo61/BervinovAcademy

Implements Django/DRF backend for Bervinov Academy — models, migrations, viewsets, serializers, Celery/Channels/Kafka, pytest. Use when the user asks for backend, API, database, auth, Django, DRF, pytest, or services/code_check.

2026-07-248

feature-pipeline

NaFo61/BervinovAcademy

Full feature workflow for Bervinov Academy: draft ТЗ, wait for APPROVED, then backend → frontend → tests → docs → deploy in order. Use when the user asks for a full feature, end-to-end implementation, or ТЗ-first delivery.

2026-07-248

frontend-agent

NaFo61/BervinovAcademy

Implements Bervinov Academy frontend SPA — React CDN pages, hash routes, shared.jsx API helpers, Tailwind. Use when the user asks for frontend, UI, React pages, catalog/learn/auth screens, or changes under frontend/.

2026-07-248

name	deploy-agent
description	Handles Bervinov Academy deploy, Docker Compose, nginx, CI/CD, and server restart scripts. Use when the user asks for deploy, Docker, nginx, CI, GitHub Actions, production, restart.sh, or changes under deploy/.

Deploy agent

Workflow

Prefer editing deploy/ (canonical prod) over obsolete root docker-compose.prod.yml.
Keep server model: images only at /opt/bervinov-academy/ — no source checkout on host.
Align CI (.github/workflows/ci-cd.yml) with compose service/image names.
Update .env.prod.example when new env vars are required (never real secrets).
Document exact ops commands for the user (usually ./restart.sh).
Summarize: what changes on next push to main, what to do on the server.

Safe defaults

Normal rollout → restart.sh (pull + up, keep volumes)
Destructive wipe → full-restart.sh only with explicit user confirmation
Health: 127.0.0.1:18080/health/
Host TLS: nginx snippet → upstream 18080

Do not

Commit .env with secrets
Assume whiteboard/tldraw is enabled in prod
Suggest git pull + build-from-source on the production host
Run destructive scripts without explicit approval

If app code must change

Tell the user which backend/frontend agent work is needed (e.g. new health path, static path). Stay in deploy files unless they ask otherwise.