For invited publishers with CLI access, deployment starts by staging a release for testing. Enable hosting before your first deploy.

Your First Deploy#

puls deploy my-game

Replace my-game with the slug Puls generated when you created your game. You can find it in the publisher dashboard.

By default, the CLI looks for your build files in a folder called ./build. If your files are somewhere else, tell it:

puls deploy my-game --dir ./dist

What Happens#

When you run puls deploy, the CLI:

1. Packages your game files
2. Uploads them to Puls
3. Gives you a test link for the staged release

The current live version stays in place until you publish the staged release.

Name Your Version#

Give your deploy a version name so you can identify it later:

puls deploy my-game --version v1.0.0

If you don’t specify a version name, one is generated automatically.

Check Your Build Folder#

Use --dry-run to confirm the local folder exists and see its file count and size without uploading:

puls deploy my-game --dry-run

This is a local check, not a full deployment test. Stage the release and open its test link to check the game in a browser.

Publish the Release#

After testing the staged release, make it live:

puls releases publish my-game v1.0.0

Players can then open the hosted game at https://my-game.puls.zone. Its public profile remains at https://puls.games/my-game.

Next: Manage Your Game