Laravel Deployment and Server Setup

This package puts your Laravel app on an Ubuntu VPS that you own, with Nginx, PHP-FPM, a database, SSL, queue workers, the scheduler and a repeatable deploy, for an app that still runs on a laptop or is updated by copying files over FTP. The server is on DigitalOcean, Hetzner, AWS or a similar provider, billed to you.

What is running when I hand over

Nginx serves the app through PHP-FPM, with MySQL or PostgreSQL on the same machine, or on a separate database server with Premium. SSL comes from Let's Encrypt and renews by itself. Queue workers run under Supervisor so they restart after a crash, and the Laravel scheduler runs from cron. On Business and Premium, Redis handles cache and queues, SSH accepts keys only, the firewall opens only web and SSH ports, and the database is backed up daily to storage away from the server.

How a deploy works

On Business and Premium a deploy pulls your Git branch into a new release folder, installs dependencies, runs migrations, then switches a symlink, so users never land on a half-updated app and the previous release is one command away. Premium adds a GitHub Actions pipeline that runs your tests before every deploy and stops the release if they fail, plus uptime and error monitoring and a Horizon dashboard for queues.

Checklist before I call it finished

• The app loads over HTTPS on your domain and a test email arrives.
• A queued job runs and the scheduler fires on time.
• You or your developer complete a deploy from the written notes without my help.

Server, backup storage and domain fees go to those providers in your name. Fixing bugs inside the application code is a separate package.