Deploying and error tracking

On the Pro and Team plans rdev helps you ship a project to production and see its errors.

Deploying with Deployer#

rdev uses Deployer, the standard deploy tool for PHP. In a Laravel or WordPress project, run:

rdev deploy init myapp

It writes a deploy.php from rdev's template and adds Deployer to the project's dev dependencies. Fill in the repository, the production host, the SSH user and the path, then deploy with vendor/bin/dep deploy production. The production server needs PHP, Composer and a web server; the production .env (or wp-config.php) lives on that server and is never deployed from here.

Your agent knows this flow too: ask it to set up deployment, and it fills in deploy.php with you before the first deploy.

Deploy approvals on the Team plan#

On the Team plan, deploy with rdev deploy run production instead of calling Deployer yourself. rdev asks for approval first: the owner and the administrators see the request on the Your team page and approve or reject it, and the deploy starts as soon as someone approves. A request nobody decides on expires after an hour.

Error tracking#

Send a project's errors to GlitchTip or Sentry, self-hosted or in their cloud. Copy the DSN from your project there, then run:

rdev errors connect myapp --dsn https://<key>@<host>/<project-id>

• Laravel: installs sentry/sentry-laravel and sets SENTRY_LARAVEL_DSN in .env. Check it with php artisan sentry:test.
• WordPress: prints the steps for the WP Sentry plugin and the line to add to wp-config.php.
• Other projects: sets SENTRY_DSN in .env for your language's Sentry SDK.