Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

deploy

Estrelas3

Forks2

Atualizado9 de março de 2026 às 18:17

Deploy the flyfun-apps web app to production on maps.flyfun.aero

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

roznet

roznet/flyfun-apps

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	deploy
description	Deploy the flyfun-apps web app to production on maps.flyfun.aero
disable-model-invocation	true

Deploy flyfun-apps to production

Use the SSH user and server IP for flyfun.aero deployment from user config. The project directory on the server is flyfun-apps.

Pre-flight checks

Ensure the working tree is clean (git status)
Ensure we are on the main branch
Show the commits that will be deployed: git log --oneline origin/main..HEAD
Check what changed to determine rebuild scope (see below)
Ask the user to confirm before proceeding

Determine rebuild scope

Get the commit currently deployed on the server:

ssh <user>@<server> "cd flyfun-apps && git rev-parse HEAD"

Then check what files changed between that commit and local HEAD:

git diff --name-only <server_commit>..HEAD

Classify the changes:

Changed files	Action needed
`Dockerfile.base`, `requirements.txt`, or rzflight/euro_aip changes	Base image rebuild (`docker compose build --no-cache base` then rebuild services)
`web/`, `shared/`, `mcp_server/`, `configs/`	Service rebuild (`docker compose build web-server` and/or `mcp-server`)
`tools/`, `.env`, `security_config.py`	Restart only (`docker compose restart web-server`)
`data/rules.json` or rules Excel files	RAG rebuild needed after deploy
Only docs, tests, `.claude/`, or non-deployed files	No rebuild needed — just pull

Tell the user what will be rebuilt and why.

Deploy steps

Push to remote: git push origin main

SSH to the server and pull:

ssh <user>@<server> "cd flyfun-apps && git pull"

Before rebuilding, check if flyfun-base image exists (it may have been pruned):
```
ssh <user>@<server> "docker images --format '{{.Repository}}:{{.Tag}}' | grep flyfun-base || echo 'MISSING'"
```
If missing, build it first: ssh <user>@<server> "cd flyfun-apps && docker compose build base"

Rebuild based on scope determined above. The most common case (code changes):

ssh <user>@<server> "cd flyfun-apps && docker compose build web-server && docker compose up -d web-server"

If base image rebuild is needed (requirements.txt, euro_aip changes):

ssh <user>@<server> "cd flyfun-apps && docker compose build --no-cache base && docker compose build web-server mcp-server && docker compose up -d"

If only restart needed:

ssh <user>@<server> "cd flyfun-apps && docker compose restart web-server"

If RAG rebuild is needed (rules.json changed):

ssh <user>@<server> "docker exec -it flyfun-web-server python /app/tools/xls_to_rules.py --out /app/data/rules.json --build-rag"

Wait a few seconds, then verify the health check:

ssh <user>@<server> "docker inspect --format='{{.State.Health.Status}}' flyfun-web-server"

Also check the endpoint is responding:

curl -s -o /dev/null -w '%{http_code}' https://maps.flyfun.aero/health

If something goes wrong

Check logs: ssh <user>@<server> "docker logs --tail 50 flyfun-web-server"
Check ChromaDB: ssh <user>@<server> "docker logs --tail 20 flyfun-chromadb"
The web container runs on port 8000 internally, exposed via WEB_PORT (default 8000)
ChromaDB runs on port 8000 internally, exposed on host port 8001
docker compose (v2 syntax, NOT docker-compose)
Containers: flyfun-web-server, flyfun-mcp-server, flyfun-chromadb

Mais deste repositório

mesmo repositório

airac-update

roznet/flyfun-apps

Update AIP data for a new AIRAC cycle (web sources + autorouter), verify changes, and optionally commit/push

2026-03-173

devserver

roznet/flyfun-apps

Start or restart the local dev server (backend + frontend) in a tmux session

2026-03-093

agent-review

roznet/flyfun-apps

Review aviation agent code changes for architecture compliance. Use when reviewing changes to shared/aviation_agent/, web/server/api/aviation_agent_chat.py, or configs/aviation_agent/. Verifies UI payload stability, tool name consistency, state management patterns, and LangGraph best practices.

2026-01-113

agent-test

roznet/flyfun-apps

Analyze aviation agent planner behavioral test results and apply improvement workflow. Use when: running planner tests, adding test cases to planner_test_cases.json, analyzing test failures, improving planner prompts, validating planner improvements, or working with tests/aviation_agent/ test infrastructure.

2026-01-113

iosapp-review

roznet/flyfun-apps

Review iOS app code changes for FlyFun EuroAIP architecture compliance. Use when reviewing Swift code in app/FlyFunEuroAIP/, checking architecture patterns, or validating adherence to designs/IOS_APP_DESIGN.md. Verifies RZFlight model reuse, composed AppState pattern, repository abstraction, and platform-specific UI patterns.

2026-01-113

ui-review

roznet/flyfun-apps

Review code changes in web/client/ts/ for compliance with architecture principles. Use when reviewing TypeScript UI code, checking store patterns, or validating separation of concerns. Verifies Zustand store as single source of truth, reactive updates, and proper component communication patterns.

2026-01-113

Deploy flyfun-apps to production

Use the SSH user and server IP for flyfun.aero deployment from user config. The project directory on the server is flyfun-apps.

Pre-flight checks

Ensure the working tree is clean (git status)

Ensure we are on the main branch

Show the commits that will be deployed: git log --oneline origin/main..HEAD

Check what changed to determine rebuild scope (see below)

Ask the user to confirm before proceeding

Determine rebuild scope

Get the commit currently deployed on the server:

ssh <user>@<server> "cd flyfun-apps && git rev-parse HEAD"

Then check what files changed between that commit and local HEAD:

git diff --name-only <server_commit>..HEAD

Classify the changes:

Changed files

Action needed

Dockerfile.base, requirements.txt, or rzflight/euro_aip changes

Base image rebuild (docker compose build --no-cache base then rebuild services)

web/, shared/, mcp_server/, configs/

Service rebuild (docker compose build web-server and/or mcp-server)

tools/, .env, security_config.py

Restart only (docker compose restart web-server)

data/rules.json or rules Excel files

RAG rebuild needed after deploy

Only docs, tests, .claude/, or non-deployed files

No rebuild needed — just pull

Tell the user what will be rebuilt and why.

Deploy steps

Push to remote: git push origin main

SSH to the server and pull:

ssh <user>@<server> "cd flyfun-apps && git pull"

Before rebuilding, check if flyfun-base image exists (it may have been pruned):

ssh <user>@<server> "docker images --format '{{.Repository}}:{{.Tag}}' | grep flyfun-base || echo 'MISSING'"

If missing, build it first: ssh <user>@<server> "cd flyfun-apps && docker compose build base"

Rebuild based on scope determined above. The most common case (code changes):

ssh <user>@<server> "cd flyfun-apps && docker compose build web-server && docker compose up -d web-server"

If base image rebuild is needed (requirements.txt, euro_aip changes):

ssh <user>@<server> "cd flyfun-apps && docker compose build --no-cache base && docker compose build web-server mcp-server && docker compose up -d"

If only restart needed:

ssh <user>@<server> "cd flyfun-apps && docker compose restart web-server"

If RAG rebuild is needed (rules.json changed):

ssh <user>@<server> "docker exec -it flyfun-web-server python /app/tools/xls_to_rules.py --out /app/data/rules.json --build-rag"

Wait a few seconds, then verify the health check:

ssh <user>@<server> "docker inspect --format='{{.State.Health.Status}}' flyfun-web-server"

Also check the endpoint is responding:

curl -s -o /dev/null -w '%{http_code}' https://maps.flyfun.aero/health

If something goes wrong

Check logs: ssh <user>@<server> "docker logs --tail 50 flyfun-web-server"

Check ChromaDB: ssh <user>@<server> "docker logs --tail 20 flyfun-chromadb"

The web container runs on port 8000 internally, exposed via WEB_PORT (default 8000)

ChromaDB runs on port 8000 internally, exposed on host port 8001

docker compose (v2 syntax, NOT docker-compose)

Containers: flyfun-web-server, flyfun-mcp-server, flyfun-chromadb