Laravel + VPS

Laravel on your own server — without DevOps

Stack provisioning, zero-downtime deploy with migrations and caches, Horizon queues and a scheduler — everything a Laravel app needs, from one panel.

Zero-downtime Horizon push-to-deploy
app.deploykin.com / Sites
shop.example.com
Laravel · PHP 8.3
Online SSL
Deploy
14 s
Horizon
active
Environment
prod
push-to-deploy queues scheduler Reverb

A ready stack in minutes

Choose the 'Laravel' server type — Deploykin installs and configures the whole stack for your app.

PHP-FPM
a version per site
Nginx
configured for public/
MySQL
databases and users
Redis
cache and queues
Composer
dependencies
Node.js
asset builds
Supervisor
daemons and queues
Git
push-to-deploy
Certbot
SSL and renewal
UFW
firewall

Nginx is configured for Laravel: root in public/, try_files to index.php, a separate PHP-FPM pool per site.

Zero-downtime

Push to Git — and Laravel is updated

Deploykin runs the whole Laravel deploy cycle: dependencies, asset builds, migrations and caches. A new release is built alongside and switched in with an atomic symlink — with not a second of downtime.

  • composer install, npm ci and asset builds
  • artisan migrate, config:cache, route:cache, view:cache
  • Releases in releases/, switching the current symlink
  • Roll back to the previous release in one click
Deploy #48 · shop.example.com
$ git clone --depth 1 → releases/20260413-1402
$ composer install --no-dev -o 
$ npm ci && npm run build 
$ php artisan migrate --force 
$ php artisan config:cache route:cache view:cache 
$ ln -sfn releases/20260413-1402 current 
→ zero-downtime · 14 s · queues restarted

Production, staging, development

The site's environment sets the install flags, APP_ENV and APP_DEBUG for you — no manual editing.

Production

APP_ENVproduction
APP_DEBUGfalse
composer--no-dev -o

An optimized install without dev dependencies, debugging off.

Staging

APP_ENVstaging
APP_DEBUGfalse
composerfull

A copy of the production environment to test releases before going live.

Development

APP_ENVlocal
APP_DEBUGtrue
composerfull

Dev dependencies and debugging on for active development.

Queues, scheduler and WebSockets

Ready-made Supervisor daemon presets — start in a couple of clicks and restart themselves.

Horizon

php artisan horizon

A dashboard and Redis queues with auto-restart.

Queue Worker

php artisan queue:work

A classic queue worker with numprocs.

Scheduler

php artisan schedule:work

Laravel's scheduled tasks without a manual cron.

Reverb

php artisan reverb:start

WebSockets with automatic /wss setup in Nginx.

Horizon — shop.example.com active
Jobs/min
1 240
Processes
12
Wait
0.4s
Failed
0
Workers restart on every deploy (horizon:terminate)
Worker nodes

Queues — on a separate server

Attach a separate VPS as a worker node: it pulls .env from the master site and runs Horizon queues while the app serves users. Heavy jobs don't affect site speed.

  • A 'Worker' server for queues
  • Automatic .env sync from the master site
  • On a worker, deploy doesn't re-run migrations
Project infrastructure
web-01 master
.env
worker-01 horizon
worker-02 horizon
.env
APP_ENV=production
APP_DEBUG=false
# обновлено при привязке базы ↓
DB_CONNECTION=mysql
DB_HOST=10.0.0.7
DB_DATABASE=shop
DB_USERNAME=shop_user
DB_PASSWORD=••••••••
.env

Manage .env from the panel

Edit environment variables in the panel, sync them with the server, and when you attach a database DB_* is filled in automatically.

  • .env editor with sync from the server
  • Auto-fill DB_* when a database is attached
  • An environment template for the whole project
  • key:generate and storage:link when the site is created
AI · MCP

Artisan commands by voice

The AI assistant and MCP can run artisan commands on the server — deploys, migrations and cache clearing can be triggered right from the chat.

run_artisan · migrate --force

Deploy Laravel without DevOps

Stack, deploy, queues and scheduler — from one panel. 7 days free after sign-up.

We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.