Run any Skill in Manus with one click

masoi-devops

Stars0

Forks0

UpdatedJune 4, 2026 at 17:14

Manage Ma Sói Docker configuration, deployment, infrastructure, environment variables, Nginx reverse proxy, health checks, and CI/CD. Use when modifying docker-compose files, Dockerfiles, nginx.conf, .env files, or preparing for VPS/cloud deployment.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

nobodyonlyc

nobodyonlyc/masoi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

3 files

SKILL.md

readonly

name	masoi-devops
description	Manage Ma Sói Docker configuration, deployment, infrastructure, environment variables, Nginx reverse proxy, health checks, and CI/CD. Use when modifying docker-compose files, Dockerfiles, nginx.conf, .env files, or preparing for VPS/cloud deployment.

Ma Sói DevOps

Workflow

Read Docker configs: docker-compose.yml (production), docker-compose.dev.yml (dev).
Read Dockerfiles: server/Dockerfile, client/Dockerfile.
Read Nginx config: client/nginx.conf.
Read environment: .env (root), server/.env, client/.env.
Check changes against references/deploy-checklist.md.
After edits, verify:
- docker compose config (validate compose syntax)
- docker compose -f docker-compose.dev.yml up -d (dev infra)
- docker compose up --build -d (full stack build)

Infrastructure Rules

Dev mode uses docker-compose.dev.yml for PostgreSQL + Redis only; server and client run natively with hot reload.
Production uses docker-compose.yml for full stack: postgres + redis + server + client/nginx.
Client Dockerfile uses multi-stage build: npm run build → Nginx serve static.
Server Dockerfile installs production deps only.
PostgreSQL schema auto-creates from server/db/init.sql on first run via Docker volume.

Environment Management

Root .env sets POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB.
Server reads DATABASE_URL, REDIS_URL, PORT from env or uses defaults.
Client reads VITE_SERVER_URL for Socket.IO connection (defaults to window.location.hostname).
Never commit .env files with production credentials.

Health & Monitoring

/health endpoint exists but only returns { ok: true } — does not verify backend connectivity.
server/check-services.js tests PostgreSQL and Redis connections at startup.
Consider adding readiness and liveness probes for container orchestration.

Nginx Configuration

Client nginx serves SPA with try_files $uri $uri/ /index.html.
API proxy passes /api/ and /socket.io/ to server container.
WebSocket upgrade headers must be set for Socket.IO.

References

Load references/deploy-checklist.md when deploying or modifying infrastructure.

More from this repository

same repository

masoi-be-testing

nobodyonlyc/masoi

Create and maintain backend unit tests, integration tests, and API tests for Ma Sói server. Covers gameEngine.js pure functions, Socket.IO handler logic, Redis/PostgreSQL data layer, authentication, room lifecycle, and timer-driven resolution. Use when adding server-side test coverage, debugging server logic, or verifying backend changes.

2026-06-040

masoi-e2e-testing

nobodyonlyc/masoi

Create and maintain automated tests for Ma Sói game engine, night/vote resolution, Socket.IO event contracts, race conditions, and role-specific edge cases. Use when adding test coverage, debugging flaky behavior, verifying concurrent action handling, or setting up CI testing.

2026-06-040

masoi-perf-security

nobodyonlyc/masoi

Audit Ma Sói server and client for performance bottlenecks, memory leaks, security vulnerabilities, rate limiting, input validation, CORS policy, timer cleanup, and room zombie detection. Use when changing socket handlers, setTimeout/setInterval patterns, Redis/PostgreSQL queries, authentication, or deploying to production.

2026-06-040

masoi-role-designer

nobodyonlyc/masoi

Design and integrate new roles into Ma Sói Online. Provides templates, file checklists, balance guidelines, and integration patterns for adding roles across server game engine, socket handlers, client hooks, UI components, and documentation. Use when planning, implementing, or reviewing new character roles.

2026-06-040

masoi-gameplay-qa

nobodyonlyc/masoi

Generate manual QA scenarios and acceptance checks for Ma Sói gameplay across player counts, role setups, night actions, vote resolution, special roles, timers, chat, and end-game history. Use before or after gameplay changes to define concrete test rooms and expected outcomes.

2026-05-280

masoi-reconnect-qa

nobodyonlyc/masoi

Review and test Ma Sói reconnect, F5 refresh, browser back, socket disconnect, resume room, stale room mapping, leave old room, and play-again recovery flows. Use when changing auth, user-room Redis mapping, disconnect handling, room_joined resume, phase timer restoration, or room reset behavior.

2026-05-280

name	masoi-devops
description	Manage Ma Sói Docker configuration, deployment, infrastructure, environment variables, Nginx reverse proxy, health checks, and CI/CD. Use when modifying docker-compose files, Dockerfiles, nginx.conf, .env files, or preparing for VPS/cloud deployment.

Ma Sói DevOps

Workflow

Read Docker configs: docker-compose.yml (production), docker-compose.dev.yml (dev).
Read Dockerfiles: server/Dockerfile, client/Dockerfile.
Read Nginx config: client/nginx.conf.
Read environment: .env (root), server/.env, client/.env.
Check changes against references/deploy-checklist.md.
After edits, verify:
- docker compose config (validate compose syntax)
- docker compose -f docker-compose.dev.yml up -d (dev infra)
- docker compose up --build -d (full stack build)

Infrastructure Rules

Dev mode uses docker-compose.dev.yml for PostgreSQL + Redis only; server and client run natively with hot reload.
Production uses docker-compose.yml for full stack: postgres + redis + server + client/nginx.
Client Dockerfile uses multi-stage build: npm run build → Nginx serve static.
Server Dockerfile installs production deps only.
PostgreSQL schema auto-creates from server/db/init.sql on first run via Docker volume.

Environment Management

Root .env sets POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB.
Server reads DATABASE_URL, REDIS_URL, PORT from env or uses defaults.
Client reads VITE_SERVER_URL for Socket.IO connection (defaults to window.location.hostname).
Never commit .env files with production credentials.

Health & Monitoring

/health endpoint exists but only returns { ok: true } — does not verify backend connectivity.
server/check-services.js tests PostgreSQL and Redis connections at startup.
Consider adding readiness and liveness probes for container orchestration.

Nginx Configuration

Client nginx serves SPA with try_files $uri $uri/ /index.html.
API proxy passes /api/ and /socket.io/ to server container.
WebSocket upgrade headers must be set for Socket.IO.

References

Load references/deploy-checklist.md when deploying or modifying infrastructure.