Adios
Apps and APIs · plans from $10/month

Deploy Laravel.Keep config, queues, and releases visible.

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

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

Candidate release

Laravel

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

LaravelPHP 8.2ComposerMySQLRedisQueues

The production path

A working Laravel 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 Laravel build you already use

Install from composer.lock and perform cache or asset preparation explicitly. Keep schema migrations separate enough to review their data impact.

Promote the version that reports healthy

Run the selected production server on the manifest port, expose a lightweight health route, and promote after required dependencies are ready.

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: laravel-app
build_cmd: composer install --no-dev --optimize-autoloader
start_cmd: php artisan serve --host=0.0.0.0 --port=8080

runtime:
  name: php@8.2
  port: 8080
  health_path: /up
Use the production process appropriate to your Laravel application and verify the health route for its installed version.

Deployable starting points

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

Inspect the Laravel starter's Composer setup, source path, runtime configuration, and one-click deployment option.

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
Review the template workflow

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 installs from the committed lockfile.
  • APP_KEY and service credentials come from secrets.
  • Writable storage has an explicit persistence strategy.
  • The web process binds to the manifest port.

Preview when…

  • Migrations modify production tables.
  • Queues or scheduled commands need a separate worker strategy.
  • User uploads depend on local filesystem state.

Questions, answered

What to know before deploying Laravel.

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

Can Adios deploy an existing Laravel 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 Laravel?

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.

Can Laravel use MySQL, PostgreSQL, and Redis?

Yes. Deploy the services your app needs, keep their credentials in Adios secrets, and inject the resulting connection settings into the Laravel process.

How should Laravel queue workers run?

Run workers as persistent processes with explicit commands and queue credentials. Verify retry, timeout, duplicate-job, and shutdown behavior independently from the web route.

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 Laravel 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 PHP

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

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 Laravel 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