---
title: "Deploy Laravel Complete — Reliable Community Template"
description: "Pinned Laravel 13 web, worker and scheduler with private MySQL and Redis."
category: "Starters"
url: https://railway.com/deploy/laravel-complete-reliable-community-temp
---

# Deploy Laravel Complete — Reliable Community Template

Pinned Laravel 13 web, worker and scheduler with private MySQL and Redis.

**[Deploy Laravel Complete — Reliable Community Template on Railway](https://railway.com/template/laravel-complete-reliable-community-temp)**

- **Creator:** Hryhory Sinenka's Projects
- **Category:** Starters

## Template content

### mysql

- **Image:** mysql:8.4.6

### redis

- **Image:** redis:7.2.10-alpine
- **Start command:** `redis-server --appendonly yes --requirepass $REDIS_PASSWORD`

### scheduler

- **Source:** hryhory-sinenka/railway-reliability-templates

### web

- **Source:** hryhory-sinenka/railway-reliability-templates
- **Health check:** /up
- **Public domain:** Yes

### worker

- **Source:** hryhory-sinenka/railway-reliability-templates

## Documentation

# Deploy and Host Laravel Complete — Reliable Community Template on Railway

Deploy a community-maintained Laravel 13 stack with separate web, queue-worker, and scheduler roles, plus private MySQL and Redis services. The template pins its application and database images, generates credentials during deployment, persists both data services, and keeps internal traffic on Railway private networking. It is not endorsed by Laravel or Railway.

## About Hosting Laravel Complete — Reliable Community Template

The web service runs database migrations before serving the application and exposes Laravel's `/up` health endpoint. Worker and scheduler services use the same pinned image and wait for the migration table before starting their long-running roles. MySQL and Redis remain private and use persistent volumes. Railway-generated application, database, and Redis secrets are shared through service references, so deployers do not need to paste credentials.

## Common Use Cases

- Production-ready Laravel application starter
- Queue-backed jobs and scheduled commands
- Private relational storage and Redis caching

## Dependencies for Laravel Complete — Reliable Community Template Hosting

- Laravel skeleton `v13.8.0` with framework `13.23.0`
- MySQL `8.4.6`
- Redis `7.2.10-alpine`
- Five Railway services; post-trial service limits or usage charges may apply

### Deployment Dependencies

- [Public template source](https://github.com/hryhory-sinenka/railway-reliability-templates)
- [Laravel v13.8.0 release](https://github.com/laravel/laravel/releases/tag/v13.8.0)
- [Laravel MIT licence](https://github.com/laravel/laravel/blob/v13.8.0/LICENSE)

### Implementation Details

The shared entrypoint selects `web`, `worker`, or `scheduler` from `APP_ROLE`. Database and cache connections use Railway private-domain references. MySQL persists at `/var/lib/mysql`; Redis persists at `/data` and requires its generated password.

## Why Deploy Laravel Complete — Reliable Community Template on Railway?

Railway keeps the five-service topology, generated secrets, private networking, health checks, and persistent volumes in one reusable template. Deployers can start from a complete Laravel stack without manually wiring queues, schedules, database credentials, or cache endpoints.

## 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/laravel-complete-reliable-community-temp