Deployments, logs and rollbacks

Every build of your app is recorded with its logs. Use them to see what's live, find out why something failed, and go back to a version that worked.

Deployments tab

The Deployments tab shows the build history for the last 30 days. Each deployment shows:

• its source (a push or a manual deploy), branch, commit and commit message,
• when it started and finished,
• its status, with a message when it failed.

Open a deployment to read its build log. You can search the log.

Runtime logs

The Logs tab shows the latest output from the running container. It refreshes while the tab is open. Choose how many lines to show (50, 100, 200 or 500) and search them to track down errors.

Redeploy or roll back

Each deployment has a Redeploy button:

• On the live commit, it rebuilds the same code, for example to pick up new environment variables.
• On an older commit, it rolls back to that version.

A new deploy replaces the live code. Rolling back doesn't change your Git history, so the next push or auto-deploy ships the branch's latest commit again.

Post-deployment commands

In Configuration you can list commands to run, in order, after each successful deploy, for example php artisan migrate --force for Laravel. Kubana never runs migrations on its own. See Laravel requirements.