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
• detected build command
• detected build output directory
• optional overrides only when detection is wrong

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

Most projects only need a name:

{
  "name": "my-game"
}

Override build settings only when Vifu cannot infer them from the project:

{
  "name": "my-game",
  "build": {
    "command": "npm run build",
    "output": "dist"
  }
}

Vifu AI is available through the SDK by default. Do not add a manifest entry for normal vifu.ai.generateText(...) calls. See the manifest reference for advanced overrides and feature disable switches.

Next Step

After setup, deploy the project:

vifu deploy

See Deploy to Vifu for the full deploy flow.