cybrix-deploy

cybrix-deploy

Prerequisites

Before deploying, ensure the user has an API token. Check in this order:

1. CYBRIX_DEPLOY_TOKEN — set automatically by Claude Code from userConfig keychain (no action needed).
2. Environment variable CYBRIX_TOKEN.
3. File ~/.config/cybrix/token.
4. File .cybrix/token in the project (gitignored).

If none exist, instruct the user exactly like this:

No Cybrix token found. Get one free at https://app.cybrix.cc/dashboard (Step 3 — "Save your API token" → Generate).

Once you have it, you can either:

• Paste it here and I'll use it for this deploy (easiest)
• Run export CYBRIX_TOKEN=<token> in your terminal to set it for this session
• Run echo <token> > ~/.config/cybrix/token to save it permanently

Then wait for the user to provide the token. If they paste it directly in chat, use it immediately — do not require them to re-run any command. The project is ready to deploy once the token is available.

Deployment workflow

Step 1 — Detect project type (heuristic)

Do not rely on a framework whitelist. Instead, look for signals and classify the project as static, server, or unknown.

Static signals (proceed with deploy):

• package.json has a build script AND output lands in dist/, out/, build/, public/, _site/, or .output/public/
• next.config.{js,ts,mjs} with output: 'export' or output: 'static'
• astro.config.{js,ts,mjs} present (default mode is static)
• vite.config.{js,ts} without SSR plugins
• _config.yml (Jekyll), config.toml or hugo.toml (Hugo), .eleventy.js / eleventy.config.js (Eleventy), zola.toml (Zola)
• Only HTML/CSS/JS files at root, no server entry point

Server signals (refuse — see below):

• Dockerfile or docker-compose.yml (unless it only copies a static dist/)
• main.go, server.go, or any *.go containing net/http or ListenAndServe
• main.py, app.py, server.py with uvicorn, gunicorn, flask, fastapi imports, or a if __name__ == '__main__' block calling app.run / serve / asyncio.run
• main.rs or server.rs with actix, axum, rocket, warp, or tokio::main
• package.json with a start script that runs node/tsx/bun on a server file (NOT next start in a static-export config)
• Gemfile with puma, unicorn, rails, or sinatra
• pom.xml or build.gradle with spring-boot
• .csproj with ASP.NET