Deployment.sh

Server deployment guides for teams that run their own servers

Practical server deployment guides written for developers who ship to servers they own. Each guide covers the full path from a fresh Ubuntu or Debian server to a production release, with commands, configuration files and the reasons behind each step, so you can follow it by hand or understand exactly what a tool does for you.

Engineer writing notes in a notebook next to a laptop and a mug in a cafe by a window
Sysadmin at a kitchen table at dawn running a server setup in a terminal on a laptop beside a router and notebook

Deploy node app to a VPS with nginx, systemd and zero downtime

Set up a locked down server, pin Node.js, build in release folders, run the app under systemd, put nginx and TLS in front and close the restart gap with health checks.

Read the guide
Data engineer at a cluttered desk with a laptop and printed charts working on a Python web app

Deploy django to production with nginx, Gunicorn, Celery and PostgreSQL

Production settings, PostgreSQL and Redis, Gunicorn under systemd, static files through nginx, Celery workers and beat, and migrations that never take the site down.

Read the guide
Developer with headphones on a train working on a JavaScript service, laptop on a fold-down table

Next.js self hosting with standalone output, caching and image optimization

Standalone builds, PM2 or systemd, a shared ISR cache for several instances, sharp for image optimization and nginx cache headers for hashed assets.

Read the guide
On-call engineer on a sofa at night checking a release on a laptop with a phone showing an alert beside

Zero downtime deployment strategies, from atomic releases to blue green

Atomic releases, graceful reloads, blue green and rolling deploys compared, plus the expand and contract pattern for database migrations.

Read the guide
Top-down view of a developer's desk with a laptop terminal, a notebook with a hand-sketched diagram of boxes and arrows and a hardware security key

Web application deployment checklist for real production servers

A verifiable checklist for servers, runtimes, the release process, secrets, databases, workers, backups, monitoring and access control.

Read the guide
Two developers in a small agency office reviewing a deploy log on a laptop, one pointing at the screen with a pen

Best laravel hosting in 2026, own server or managed platform

Own servers, managed platforms and server panels compared for Laravel, with the PHP-FPM, OPcache, Horizon and scheduler setup that holds up in production.

Read the guide
CTO crouching at an open server cabinet in a small office server room lit by cool blue LED strips, laptop on the rack rail showing a dark terminal

PaaS vs VPS cost for a team of five running four apps

Worked arithmetic with stated assumptions and round illustrative prices, including seats, staging and the cost of time, so you can rebuild the model with real numbers.

Read the guide

Put these guides into practice on your own servers

Deployment provisions your servers and runs every step from these guides on each push, with zero downtime releases and one click rollback. Paste a public repository into the demo on the home page to see the detected stack and your deploy plan.