---
title: "Deploy Laravel 13 Blade MySQL [Oct 26]"
description: "Laravel 13.37 Blade starter with MySQL. Updated Oct 26"
category: "Starters"
url: https://railway.com/deploy/JL9ADu
---

# Deploy Laravel 13 Blade MySQL [Oct 26]

Laravel 13.37 Blade starter with MySQL. Updated Oct 26

**[Deploy Laravel 13 Blade MySQL [Oct 26] on Railway](https://railway.com/template/JL9ADu)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/JL9ADu/manifest.json

- **Creator:** Marco Quintella's Projects
- **Category:** Starters
- **Total deploys:** 32

## Template content

### laravel-blade-mysql

- **Source:** https://github.com/marco-quintella/laravel-blade-mysql
- **Public domain:** Yes

### MySQL https://devicons.railway.app/i/mysql.svg

- **Image:** mysql:9
- **Start command:** `docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0`

## Documentation

# Deploy and Host Laravel 13 Blade MySQL on Railway

Laravel 13.37 (16 October 2026) Blade starter with MySQL. One click provisions the database, injects `DB_URL`, runs migrations, and serves the app with FrankenPHP.

[![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/template/JL9ADu?referralCode=2Sbs5r)

## About Hosting Laravel 13 Blade MySQL

Railpack builds this repo on PHP 8.4 and starts FrankenPHP with the document root at `public`. The start script runs `php artisan migrate --force` before the server listens. Railway's healthcheck is `GET /up`. The app trusts Railway's proxy, so pages and assets stay on HTTPS.

The MySQL service is part of the template. Its connection string is wired to `DB_URL`. If the wizard also sets `DB_CONNECTION=sqlite` (the skeleton default), a present `DB_URL` still selects MySQL. `ext-pdo_mysql` is required in `composer.json`, so Railpack installs the driver even when `DB_CONNECTION` is not `mysql`.

## Why Deploy Laravel 13 Blade MySQL on Railway?

- October 2026 framework: Laravel 13.37, PHP 8.4, Vite 8.3, Tailwind CSS 4.3.
- MySQL is provisioned with the app. No manual connection form.
- Migrations run on every deploy and are safe to repeat.
- `GET /up` is the healthcheck. Logs from the start script go to the deploy logs.

## Common Use Cases

- Start a Blade app that already talks to MySQL on Railway.
- Confirm a production deploy path before adding auth, queues, or your own routes.
- Fork the skeleton and keep the `DB_URL` connection rule.

## Dependencies for Laravel 13 Blade MySQL Hosting

### Deployment Dependencies

- Laravel 13.37 and PHP 8.4
- MySQL 9 (the template service). `DB_URL` is `${{MySQL.MYSQL_PUBLIC_URL}}`
- FrankenPHP, installed by Railpack
- Vite 8.3 and Tailwind CSS 4.3, built during the Railpack install

## What you get

| Service | Description |
|---|---|
| Laravel 13.37 app | Blade starter served by FrankenPHP |
| MySQL 9 | Managed database, connected via `DB_URL` |

## Local development

```bash
cp .env.example .env
composer install
npm install
npm run build
php artisan key:generate
php artisan serve
```

Without `DB_URL`, the app uses SQLite. Set `DB_URL` to a MySQL URL when you want the same connection the template uses.

## Notes

- **Database**: `config/database.php` uses MySQL whenever `DB_URL` is set, including when `DB_CONNECTION` is `sqlite`.
- **Migrations**: run on every deploy.
- **Healthcheck**: `/up`, registered in `bootstrap/app.php`.
- **Logging**: the start script prints migration output to the deploy logs (`railway logs`).


## Similar templates

- [open-excalidraw](https://railway.com/deploy/open-excalidraw) — Self-hostable collaborative drawing built on Excalidraw
- [caring-vibrancy](https://railway.com/deploy/caring-vibrancy) — Deploy and Host caring-vibrancy with Railway
- [Appsmith](https://railway.com/deploy/appsmith-1) — Low-code platform for internal tools, dashboards, and admin panels.

Open this page in a browser: https://railway.com/deploy/JL9ADu