synpulse8-opensourcesynpulse8-opensource/pulse8-ai-cortex-knowledge-vault/.cursor/skills/cortex-deploy/SKILL.md

cortex-deploy

Skill15 starsChanged 5 months agoApache-2.0View on GitHub

Cortex deployment — Docker Compose, env_check.sh, CORTEX_* env vars, EC2/rsync, logs. Use for production setup, container config, or server debugging.

Reads credentials

In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cortex-apiSkill
- cortex-authSkill
- cortex-compilerSkill
- cortex-contributingSkill
- cortex-feedbackSkill
- cortex-graph-searchSkill
- cortex-mcpSkill
- cortexSkill
- cortex-vaultSkill

The file

Create a free account to mount

Files

SKILL.md

Cortex deploy

Quick start

./scripts/env_check.sh    # interactive .env generation
docker compose up -d
curl http://localhost:8420/api/v1/health

Docker Compose (`docker-compose.yml`)

Service	Port	Notes
`cortex`	8420	API + MCP HTTP
volumes	`vault`, optional `/ingest`	`CORTEX_VAULT_PATH`, bulk source dir

Env mapping uses CORTEX_ prefix in compose (e.g. CORTEX_TEAMS_WEBHOOK_URL, CORTEX_API_KEY).

Environment dual naming

Settings accept either:

VAULT_PATH or CORTEX_VAULT_PATH
API_KEY or CORTEX_API_KEY
TEAMS_WEBHOOK_URL or CORTEX_TEAMS_WEBHOOK_URL

scripts/env_check.sh writes unprefixed names; compose often maps to CORTEX_*.

Production sync (example)

rsync -avz -e "ssh -i ~/.ssh/key" ./vault/ user@host:~/vault/
ssh user@host 'cd app && docker compose restart cortex'

Host paths in bulk-ingest must exist inside the container (mount at /ingest).

Logs

docker logs cortex 2>&1 | tail -100
# Access lines → stdout (uvicorn.access)
# App logs → stderr (cortex.*)

Health checks

GET /api/v1/health
Graph: GET /api/v1/graph/stats (with auth if enabled)

Teams notifications

Optional TEAMS_WEBHOOK_URL + TEAMS_APP_BASE_URL for feedback cards (cortex/notify/teams.py). Validated in env_check.sh.

Related skills

Auth: cortex-auth
Compiler bulk paths: cortex-compiler

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free