Skip to main content

server-management

This skill should be used when the user asks to "start the server", "restart the server", "check server status", "is the server running", "server health", "server version", "rebuild container", or when the agent needs to ensure the server is running before testing. Use proactively before any manual or emulator testing, before asking the user to verify something in the browser. Also use when the user reports stale behavior or says "it's not showing my changes".

Ir a la instalación

Datos de origen

Repositorio
flavordrake/mobissh
Última actividad en el origen
21 de septiembre de 2026 a las 13:43
Idioma detectado de SKILL.md
inglés
Estrellas
2
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
2 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
server-management
description
This skill should be used when the user asks to "start the server", "restart the server", "check server status", "is the server running", "server health", "server version", "rebuild container", or when the agent needs to ensure the server is running before testing. Use proactively before any manual or emulator testing, before asking the user to verify something in the browser. Also use when the user reports stale behavior or says "it's not showing my changes".
version
0.2.0
# Server Management MobiSSH runs as a Docker container in production. Code changes require a container rebuild. ## Production: Docker container (`mobissh-prod`) The production server runs via `docker-compose.prod.yml` with built-in Tailscale. The container copies `public/` and `server/` at build time -- it does NOT hot-reload. ### Commands ```bash # Rebuild and deploy (after code changes) scripts/container-ctl.sh restart # Check status (health + code-currency check) scripts/container-ctl.sh status # Ensure current (idempotent: rebuilds only if stale) scripts/container-ctl.sh ensure # View logs docker logs mobissh-prod --tail 50 # Verify code is current docker exec mobissh-prod grep '<marker>' /app/public/native.html # Shell into container docker exec -it mobissh-prod sh ``` ### "My changes aren't showing" 1. Did you rebuild the container? (`scripts/container-ctl.sh restart`) — the image COPYs `public/` and `server/` at build time. 2. Is the container serving HEAD? (`scripts/container-ctl.sh status`) 3. Verify: `docker exec mobissh-prod grep '<your change>' /app/server/index.js` There is no build step: #1205 retired the PWA's TypeScript sources, so `public/` is shipped verbatim. ## Local server `scripts/server-ctl.sh` manages a local Node.js process on port 8081. This is NOT used for user-facing testing — use the prod container. ```bash scripts/server-ctl.sh ensure # start or restart until healthy at HEAD scripts/server-ctl.sh status # health check + version gate scripts/server-ctl.sh start # start if not running scripts/server-ctl.sh stop # stop server scripts/server-ctl.sh restart # force restart ``` `scripts/server-ctl.sh ensure` is the local-server lifecycle; the prod container is `scripts/container-ctl.sh`. ## Environment Variables | Variable | Default | Purpose | |---|---|---| | `PORT` | 8081 | Server listen port | | `TS_AUTHKEY` | (none) | Tailscale auth key for container | | `TS_HOSTNAME` | mobissh | Tailscale hostname | | `TS_SERVE` | 1 | Enable tailscale serve (skips auth in container) | ## Test sshd container A separate Docker Compose file (`docker-compose.test.yml`) runs an sshd container for testing: ```bash docker compose -f docker-compose.test.yml up -d test-sshd # start test sshd on port 2222 ``` Note: test sshd is a simple container with no lifecycle script — raw `docker compose` is acceptable here.
Ver en GitHub