Adios
Apps and APIs · plans from $10/month

Deploy PHP.Keep Composer and runtime config together.

Install production dependencies, start the application on a declared port, verify health, and connect the promoted release to domains and TLS.

Deploy my projectDeploy a template
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

PHP

Healthy

SOURCE

Git

REGION

de

ROUTE

HTTPS

01Source received

02Build completed

03Runtime started

04Health check passed

Promoted route

production.adios.run

A production path for

PHP 8.2LaravelSymfonyComposerAPIsWeb apps

The production path

A working PHP project still needs a safe release.

The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.

Keep the PHP build you already use

Install from composer.lock with production flags and keep framework preparation in a visible build command. The source remains portable and reviewable.

Promote the version that reports healthy

Start the framework's intended production process on the configured port and use a readiness endpoint that does not expose secrets or mutate data.

Trace production back to source

Build output, runtime logs, health state, secrets, domains, and the promoted release stay attached to the project instead of being split across unrelated tools.

From source to release

Three steps keep the deployment path reviewable.

Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.

  1. 01

    Start with source or a template

    Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.

    $adios login
  2. 02

    Review the deployment contract

    Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.

    $git diff -- adios.yaml
  3. 03

    Deploy and inspect the result

    Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.

    $adios up
adios.yaml
Your project
name: php-app
build_cmd: composer install --no-dev --optimize-autoloader
start_cmd: php -S 0.0.0.0:8080 -t public

runtime:
  name: php@8.2
  port: 8080
  health_path: /healthz
The built-in server is suitable for a minimal starter; use the production process recommended by your framework for a real application.

Deployable starting points

Start PHP from a template when the repository is not ready.

Compare Laravel, Symfony, and minimal PHP starters with Composer and Adios configuration already present.

API starters

PHP Laravel

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPComposer
Template key
php-laravel
Runtime
php
Repository
templates
Source path
php/laravel
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/laravel
adios up
DeployView source

API starters

PHP Symfony

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPComposer
Template key
php-symfony
Runtime
php
Repository
templates
Source path
php/symfony
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/symfony
adios up
DeployView source

API starters

PHP CakePHP

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPComposer
Template key
php-cakephp
Runtime
php
Repository
templates
Source path
php/cakephp
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/cakephp
adios up
DeployView source

API starters

PHP CodeIgniter 4

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPComposer
Template key
php-codeigniter4
Runtime
php
Repository
templates
Source path
php/codeigniter4
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/codeigniter4
adios up
DeployView source

API starters

PHP Yii 2

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPComposer
Template key
php-yii2
Runtime
php
Repository
templates
Source path
php/yii2
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/yii2
adios up
DeployView source

API starters

PHP 8.2

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPComposer
Template key
php
Runtime
php
Repository
templates
Source path
php/8.2
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/8.2
adios up
DeployView source
See a complete PHP deployment

Before production

Verify the workload.Then promote it.

The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.

Ready when…

  • composer install works from the committed lockfile.
  • The production process binds to the manifest port.
  • Writable directories have an explicit persistence strategy.
  • Application keys and database passwords use secrets.

Preview when…

  • Composer packages need operating-system extensions.
  • Uploads or generated files are written to local disk.
  • Framework caches or migrations run during deployment.

Questions, answered

What to know before deploying PHP.

Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.

Can Adios deploy an existing PHP project?

Yes. Run the Adios CLI from the project root, keep the repository and dependency files you already use, and add an adios.yaml file that describes the production build, start command, port, and health path.

Do I need Docker to deploy PHP?

Not for a standard supported runtime. Use the project's normal production commands in adios.yaml. If the build needs unusual operating-system packages or native libraries, verify those dependencies in a preview before promotion.

Which PHP frameworks have templates?

The catalog includes Laravel, Symfony, CakePHP, CodeIgniter 4, Yii 2, and a minimal PHP 8.2 starter.

Can PHP applications use MySQL or Redis?

Yes. Deploy the required data service, store its credentials as secrets, and inject connection values into the PHP process. Verify application reconnect behavior after a service restart.

What happens when the build or health check fails?

The candidate release keeps its build and runtime output for inspection. It must report healthy before it becomes the promoted version serving the application route.

Can I start from a template instead of an existing repo?

Yes. This page links to the closest official Adios PHP starters. Inspect the exact source variant, deploy it in the console, or clone it locally and run adios up.

Related deployment paths

Connect the rest of the stack.

Browse all deployment pages

Deploy Laravel

Install production dependencies, start the Laravel web process, verify health, and connect database, cache, queues, secrets, logs, and domains deliberately.

Deploy MySQL

Start MySQL 8 with persistent storage, create a dedicated application database and user, protect both passwords, and verify data after restart.

Deploy Redis

Start Redis 7 for cache, session, pub/sub, or fast state workloads, then verify connectivity, persistence expectations, eviction, and dependency failure behavior.

Deploy Adios workflows

Deploy scheduled jobs, webhook processors, approval gates, maintenance tasks, and operational automation from a versioned workflow manifest.

The first release

Deploy PHP with the source and evidence attached.

Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.

Start with AdiosCompare plans