Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy Laravel on Deployxa.
Deploy Laravel with Composer builds, config and route caching, database migrations, managed MySQL or PostgreSQL, and HTTPS.
- 01Detected fromartisan · composer.json
- 02RuntimePHP-FPM with Nginx
- 03Build commandcomposer install --no-dev --optimize-autoloader
- 04Web rootpublic
- 05Releasephp artisan migrate --force
- 06HTTPSLet's Encrypt
01 / Quickstart
Deploy from your terminal.
Install the CLI and deploy the Laravel project in your current directory, or connect the repository in the console for push-to-deploy.
- Typical database: MySQL or PostgreSQL
- Build and start commands can be overridden
- Secrets stay out of build logs
$ npm install -g @deployxa/cli$ deployxa login$ deployxa deploy
02 / Guide
How Laravel goes to production.
- 01 /
Connect the repository
Deployxa finds composer.json and artisan, selects PHP and serves the public/ directory.
- 02 /
Attach a database
Add managed MySQL or PostgreSQL; the connection details are injected as environment variables.
- 03 /
Cache and migrate
Run config:cache, route:cache and migrate --force so the release starts with an up-to-date schema.
- 04 /
Go live
Traffic switches once the new release passes its health check.
03 / Configuration
Environment variables.
Set these in project settings. Values are never written to build logs.
| Variable | Purpose | Example |
|---|---|---|
APP_ENV | Application environment | production |
APP_KEY | Encryption key from php artisan key:generate | base64:... |
APP_DEBUG | Keep detailed errors off in production | false |
DB_CONNECTION | Database driver | mysql |
CACHE_STORE | Cache backend | redis |
04 / Included
What every deploy gets.
Isolated builds
Every push builds in its own sandbox with cached dependencies and layers.
Managed databases
Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.
HTTPS by default
Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.
Health-checked releases
Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.
Push to deploy
Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.
05 / FAQ
Laravel questions.
How are migrations handled?
php artisan migrate --force runs during the release. If it fails, the deploy stops and the previous release keeps serving traffic.
Where do uploaded files go?
Use a persistent volume or S3-compatible storage for storage/app. Container filesystems are replaced on every deploy.