La configuration VPS qui fonctionne vraiment : Node.js, PM2, Nginx et déploiements sans interruption | Akousa

javascript

// ecosystem.config.js
module.exports = {
  apps: [
    {
      name: "myapp",
      script: "node_modules/.bin/next",
      args: "start -p 3002",
      cwd: "/var/www/example.com",
      instances: 2,
      exec_mode: "cluster",
      max_memory_restart: "500M",
      env: {
        NODE_ENV: "production",
        PORT: 3002,
      },
      // Arret gracieux
      kill_timeout: 5000,
      listen_timeout: 10000,
      wait_ready: false,
      // Logging
      log_date_format: "YYYY-MM-DD HH:mm:ss Z",
      error_file: "/var/log/pm2/myapp-error.log",
      out_file: "/var/log/pm2/myapp-out.log",
      merge_logs: true,
      // Redemarrage automatique en cas d'echec
      autorestart: true,
      max_restarts: 10,
      min_uptime: "10s",
      // Ne pas surveiller en production
      watch: false,
    },
  ],
};

nginx

# /etc/nginx/sites-available/example.com
 
upstream node_app {
    server 127.0.0.1:3002;
    keepalive 64;
}
 
server {
    listen 80;
    listen [::]:80;
    server_name example.com www.example.com;
 
    # Rediriger tout le HTTP vers HTTPS
    return 301 https://$host$request_uri;
}
 
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name example.com www.example.com;
 
    # SSL (gere par Certbot — ces lignes sont ajoutees automatiquement)
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
    include /etc/letsencrypt/options-ssl-nginx.conf;
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
 
    # En-tetes de securite
    add_header X-Frame-Options "SAMEORIGIN" always;
    add_header X-Content-Type-Options "nosniff" always;
    add_header X-XSS-Protection "1; mode=block" always;
    add_header Referrer-Policy "strict-origin-when-cross-origin" always;
    add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;
 
    # Compression gzip
    gzip on;
    gzip_vary on;
    gzip_proxied any;
    gzip_comp_level 6;
    gzip_min_length 256;
    gzip_types
        text/plain
        text/css
        text/javascript
        application/javascript
        application/json
        application/xml
        image/svg+xml
        application/wasm;
 
    # Parametres du proxy
    location / {
        proxy_pass http://node_app;
        proxy_http_version 1.1;
 
        # En-tetes
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
 
        # Support WebSocket (au cas ou vous en auriez besoin)
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
 
        # Timeouts — genereux mais pas infinis
        proxy_connect_timeout 60s;
        proxy_send_timeout 60s;
        proxy_read_timeout 60s;
 
        # Buffering — laissez Nginx gerer les clients lents
        proxy_buffering on;
        proxy_buffer_size 16k;
        proxy_buffers 4 32k;
        proxy_busy_buffers_size 64k;
    }
 
    # Assets statiques Next.js — laissez Nginx les servir directement
    location /_next/static/ {
        alias /var/www/example.com/.next/static/;
        expires 365d;
        access_log off;
        add_header Cache-Control "public, immutable";
    }
 
    # Fichiers statiques publics
    location /static/ {
        alias /var/www/example.com/public/static/;
        expires 30d;
        access_log off;
    }
 
    # Bloquer l'acces aux fichiers caches (dotfiles)
    location ~ /\. {
        deny all;
        access_log off;
        log_not_found off;
    }
}

bash

#!/bin/bash
# deploy.sh — deploiement quasi sans interruption
 
set -euo pipefail
 
APP_DIR="/var/www/example.com"
APP_NAME="myapp"
LOG_FILE="/var/log/deploy.log"
HEALTH_URL="http://localhost:3002"
MAX_RETRIES=10
RETRY_INTERVAL=3
 
log() {
    echo "[$(date '+%Y-%m-%d %H:%M:%S')] $1" | tee -a "$LOG_FILE"
}
 
log "=== Deploy started ==="
 
cd "$APP_DIR"
 
# Recuperer le dernier code
log "Pulling latest changes..."
git pull origin main 2>&1 | tee -a "$LOG_FILE"
 
# Installer les dependances
log "Installing dependencies..."
npm install --legacy-peer-deps 2>&1 | tee -a "$LOG_FILE"
 
# Build
log "Building application..."
rm -rf .next
npm run build 2>&1 | tee -a "$LOG_FILE"
 
if [ $? -ne 0 ]; then
    log "ERROR: Build failed. Aborting deploy."
    exit 1
fi
 
# Recharger PM2 (sans interruption en mode cluster)
log "Reloading PM2..."
pm2 reload "$APP_NAME" 2>&1 | tee -a "$LOG_FILE"
pm2 save 2>&1 | tee -a "$LOG_FILE"
 
# Verification de sante avec retries
log "Running health check..."
for i in $(seq 1 $MAX_RETRIES); do
    HTTP_CODE=$(curl -s -o /dev/null -w '%{http_code}' "$HEALTH_URL" 2>/dev/null || echo "000")
    if [ "$HTTP_CODE" = "200" ]; then
        log "Health check passed (HTTP $HTTP_CODE)"
        log "=== Deploy completed successfully ==="
        exit 0
    fi
    log "Health check attempt $i/$MAX_RETRIES (HTTP $HTTP_CODE). Retrying in ${RETRY_INTERVAL}s..."
    sleep $RETRY_INTERVAL
done
 
log "ERROR: Health check failed after $MAX_RETRIES attempts"
log "Rolling back to previous PM2 state..."
pm2 restart "$APP_NAME" 2>&1 | tee -a "$LOG_FILE"
exit 1

La configuration VPS qui fonctionne vraiment : Node.js, PM2, Nginx et déploiements sans interruption

Commencez par la sécurité, pas le code

Creez un utilisateur non-root

Configurez l'authentification par cle SSH

Pare-feu avec UFW

Fail2Ban

Mises a jour de sécurité automatiques

Node.js : utilisez NVM, pas apt

PM2 : le gestionnaire de processus qui vaut le coup

Installation et configuration

La configuration ecosystem

Script de demarrage

Rotation des logs

Nginx : le reverse proxy qui fait plus que vous ne pensez

Installation

La configuration

SSL en cinq minutes

Vérifier le renouvellement automatique

Le script de déploiement

Quand ca casse a 2h du matin

"Le site est down"

"La mémoire ne cesse d'augmenter"

"Le certificat SSL a expire"

"Le disque est plein"

La commande que je lancé chaque matin

Ce que la plupart des guides ne vous diront pas

La checklist complete

Est-ce "enterprise-grade" ?

Articles similaires

Monorepos in 2026: Nx, Turborepo, and the Lessons Nobody Shares

YAML Validator Guide: Catch Config Errors Before Deploy