Stack detection
Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.
Deploy PHP on Deployxa.
Deploy PHP applications with Composer dependency installs, Nginx and PHP-FPM, managed MySQL and HTTPS.
- 01Detected fromcomposer.json · index.php
- 02RuntimePHP-FPM with Nginx
- 03Build commandcomposer install --no-dev
- 04Web rootpublic
- 05HTTPSLet's Encrypt
01 / Quickstart
Deploy from your terminal.
Install the CLI and deploy the PHP project in your current directory, or connect the repository in the console for push-to-deploy.
- Typical database: MySQL
- 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 PHP goes to production.
- 01 /
Connect the repository
Composer dependencies are installed and Nginx serves your web root through PHP-FPM.
- 02 /
Attach a database
Add managed MySQL; credentials are injected as environment variables.
- 03 /
Go live
The app is health-checked and served over HTTPS.
03 / Configuration
Environment variables.
Set these in project settings. Values are never written to build logs.
| Variable | Purpose | Example |
|---|---|---|
PHP_MEMORY_LIMIT | Memory limit per request | 256M |
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
PHP questions.
Can I set my own web root?
Yes. Point the web root at the directory that holds your front controller, such as public/.