Setup For Deployment

vifu setup prepares an existing game project for Vifu deploy. You can run it explicitly, or let vifu deploy start the same setup flow when configuration is missing.

Run Setup

cd path/to/your-game
vifu setup

The CLI detects the project and asks for:

• game name
• version
• HTML entry
• build command
• build output directory
• whether to enable Vifu AI, cloud save, or companion bridge

For CI or scripts, accept detected defaults without prompts:

vifu deploy --yes

Use strict mode when configuration must already exist:

vifu deploy --no-setup

Common Project Shapes

Static HTML:

{
  "main": { "url": "index.html", "engine": "vanilla" },
  "build": { "output": "target/web" }
}

Vite, Angular, Phaser, or other bundled apps:

{
  "main": { "url": "index.html", "engine": "phaser" },
  "build": {
    "command": "npm run build",
    "output": "dist"
  }
}

AI-native games should declare Vifu AI use:

{
  "ai": {
    "dialogue": { "role": "npc" },
    "budget": { "mode": "demo", "turns": 8 },
    "fallback": "deterministic"
  }
}

Next Step

After setup, deploy the project:

vifu deploy

See Deploy to Vifu for the full deploy flow.