Make digitalize mainteinace great again

[Marinofull]

Digitalize Maintenance Mode (Docker Compose + Nginx)

This repo contains a static maintenance page (index.html + assets/). The simplest, maintainable way to switch what Nginx serves is to run an alternative Nginx container under a Docker Compose profile that binds the same ports (80/443) and serves only this static page.

Because only one container can bind 80/443 at a time, you must stop the “prod” Nginx container before starting the maintenance one (and vice‑versa).

1) Add this repo as a git submodule

On the server that runs your docker-compose.yml (and already has SSH access to GitHub), add this maintenance page repo as a submodule next to the compose file:

# From the repo that contains docker-compose.yml
git submodule add -b digitalize git@github.com:oxeanbits/maintenance.git maintenance
git submodule update --init --recursive

To update the maintenance page later:

git submodule update --remote --merge maintenance

2) Add a maintenance Nginx service (profile-based)

Edit your docker-compose.yml:

1. Put your existing nginx behind a profile (e.g. prod).
2. Add a new nginx_maintenance service behind a maintenance profile.

Example (only the relevant parts):

services:
  nginx:
    image: nginx:1.29.3-alpine
    container_name: nginx
    profiles: ["prod"]
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./etc-nginx/nginx/nginx.conf:/etc/nginx/nginx.conf
      - ./etc-nginx/nginx/.htpasswd:/etc/nginx/.htpasswd
      - ./etc-nginx/nginx/conf.d:/etc/nginx/conf.d
      - ./etc-nginx/certbeta/conf:/etc/letsencrypt
      - ./etc-nginx/certbeta/www:/var/www/certbot
    # keep the rest as-is...

  nginx_maintenance:
    image: nginx:1.29.3-alpine
    container_name: nginx-maintenance
    profiles: ["maintenance"]
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      # Maintenance page (this repo copied to the server)
      - ./maintenance:/usr/share/nginx/html:ro

      # Maintenance Nginx config (create these files/directories)
      - ./etc-nginx/nginx/nginx.conf:/etc/nginx/nginx.conf:ro
      - ./etc-nginx/nginx/conf.d-maintenance:/etc/nginx/conf.d:ro

      # Keep certbot working (optional but recommended)
      - ./etc-nginx/certbeta/conf:/etc/letsencrypt
      - ./etc-nginx/certbeta/www:/var/www/certbot

Notes:

• Reusing ./etc-nginx/nginx/nginx.conf is optional; you can also mount a fully separate nginx-maintenance.conf if you prefer.
• If you keep certbot renewal running, make sure the maintenance Nginx also serves the ACME webroot path.

3) Add a maintenance Nginx vhost

Create ./etc-nginx/nginx/conf.d-maintenance/default.conf:

server {
  listen 80 default_server;
  server_name _;

  # ACME HTTP-01 challenge (certbot webroot)
  location ^~ /.well-known/acme-challenge/ {
    root /var/www/certbot;
  }

  root /usr/share/nginx/html;
  index index.html;

  location / {
    try_files /index.html =200;
    add_header Cache-Control "no-store" always;
  }
}

If you need HTTPS during maintenance, add an additional server { listen 443 ssl ... } block that matches how your current production Nginx loads certificates from /etc/letsencrypt.

4) Switch into maintenance mode

From the folder containing docker-compose.yml:

# Stop prod nginx (frees ports 80/443)
docker compose stop nginx

# Start maintenance nginx
docker compose --profile maintenance up -d nginx_maintenance

5) Switch back to production

# Stop maintenance nginx
docker compose stop nginx_maintenance

# Start prod nginx again
docker compose --profile prod up -d nginx