Laravel on Your Own Server, Production Ready

    1

    Your coding agent hardens and deploys your Laravel app on your own VPS: env, caches, OPcache, queue workers, cron, logs, backups and zero downtime releases, ending with a go-live checklist.

    $7

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Laravel on Your Own Server, Production Ready

    Example session with this skill installed

    We deploy with git pull on a VPS and sometimes changes don't show up. Make our deploy safe and check we're ready for production.

    • Read your context and instructions
    • Compiled the laravel on your

    Summary (example run). Ubuntu, Nginx, PHP 8.3 FPM, Laravel 12. Two causes for "changes don't show up": OPcache with validate_timestamps=0 and no FPM reload, and queue workers never restarted. Moved you to release folders with a symlink swap.

    Go-live checklist

    CheckBeforeAfter
    Debug ModeONOFF
    Config, routes, views, eventsnot cachedCACHED
    env() outside config/3 calls0
    PHP-FPM reload on deploynoyes
    Workers under Supervisorno, nohup4 RUNNING
    job timeout < retry_after < stopwaitsecs120 / 90 / none60 / 90 / 120
    Logssingle file, 2.1 GBdaily, 14 days
    Backup restored onceneveryes, 4 min

    Deploy

    APP_DIR=/var/www/app REPO=git@host:org/app.git BRANCH=main ./deploy.sh
    ./deploy.sh rollback
    

    Builds in releases/<timestamp>, shares .env and storage/, swaps current, reloads FPM, restarts workers, checks /up.

    Next steps

    • Point your uptime monitor at /up.
    • The posts.slug rename needs two deploys: add the new column first, drop the old one later.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    You run Laravel on your own server, not Laravel Cloud. Things work, mostly. But a deploy sometimes "does nothing", a job runs twice, the log file fills the disk, and nobody has ever restored a backup.

    This skill walks your agent through the setup in a fixed order. Each step is safe to ship on its own.

    What it does

    • Reads the server before changing it: PHP version, modules, Nginx, Supervisor, crontab, php artisan about.
    • Sets the .env right and finds env() calls outside config/ that break once config is cached.
    • Caches config, routes, views and events on every deploy.
    • Sets OPcache, and reloads PHP-FPM on deploy so new code shows up.
    • Runs queue workers or Horizon under Supervisor, with timeouts in the right order so jobs don't run twice.
    • Sets the scheduler cron, daily logs, and backups you actually test with a restore.
    • Gives you a release folder deploy script with an atomic symlink swap, a health check and a rollback.

    What you get Config files for Supervisor and OPcache, a deploy script, and a go-live checklist where each line is ticked by running a command, not from memory.

    What it doesn't do It doesn't cover Laravel Cloud or Vapor. It won't run php artisan down for a normal deploy, and it prefers a forward fix over a down migration on real data.

    Requires sudo access for PHP-FPM reloads and Supervisor management. Not compatible with Laravel Cloud. Designed for Linux-based VPS or bare metal servers.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Requires

    Laravel 10+ app
    Linux server with SSH, Nginx and PHP-FPM
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables

    File Scopes

    config/*.php
    .env.example
    deploy.sh
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Yes, it targets any self-hosted box: VPS, bare metal, Forge-style or Ploi-style. Not Laravel Cloud.

    No. It sets up plain queue workers or Horizon under Supervisor, you pick one.

    Covered. Where a command or setting differs on 10 (caching, failed jobs table, log days), it gives the Laravel 10 way.

    New in DevOps & Cloud