Project Console

The Console tab on a project lets you run a one-off command against the currently deployed release, across one or more servers, without going through a full deployment.

Running a command

On the Console tab:

• Command: a shell command or script (multi-line is fine), e.g. php artisan cache:clear.
• Run As User (optional): runs the command via non-interactive sudo as that user, same as a deploy step’s Run As. Leave blank to run as the server’s configured SSH user.
• Servers (only shown when the project has more than one): leave every box unchecked to run on all servers, or check specific ones to target a subset.

The command runs with its working directory set to <deploy_path>/current on each targeted server, in order. If a server has never had a successful deployment (no current symlink yet), that server’s run fails with no current release under <deploy_path> instead of running in the wrong place.

Each run is capped at 2 minutes per server. The console is meant for quick operational commands, not long-running jobs.

Audit trail

Every console run is recorded before execution starts (so an interrupted run still leaves a trace) and updated with its result afterward: the command, which user ran it, which servers, the Run As user (if any), combined output, exit code, duration, and overall status (success or failed).

Past runs are listed on the Console tab, newest first, each collapsed to its command and status. Expand one to see its full output.