Installation multiple dtable-servers¶

services:
  dtable-server-proxy:
    image: nginx:1.27.5-alpine
    container_name: dtable-server-proxy
    restart: unless-stopped
    ports:
      - "5000:5000"
    volumes:
      - ./nginx-proxy.conf:/etc/nginx/nginx.conf:ro
    networks:
      - frontend-net
    extra_hosts:
      - "dtable-web:10.0.0.2"
      - "dtable-db:10.0.0.3"
      - "dtable-server:10.0.0.4"
      - "dtable-server-2:10.0.0.5"
    logging:
      driver: json-file
      options:
        # Maximum size per file
        max-size: 10m
        # Maximum number of files
        max-file: 3

  networks:
    frontend-net:
      name: frontend-net

services:
  dtable-server-proxy:
    image: caddy:2.11.2-alpine
    container_name: dtable-server-proxy
    restart: unless-stopped
    ports:
      - 5000:5000
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
    networks:
      - backend-seatable-net
    healthcheck:
      test: ["CMD-SHELL", "curl --fail http://localhost:2019/metrics || exit 1"]
      start_period: 20s
      interval: 20s
      timeout: 5s
      retries: 3
    extra_hosts:
      - "dtable-web:10.0.0.2"
      - "dtable-db:10.0.0.3"
      - "dtable-server:10.0.0.4"
      - "dtable-server-2:10.0.0.5"
    logging:
      driver: json-file
      options:
        max-size: 10m
        max-file: 3

worker_processes auto;

events {
  worker_connections 4096;
}

http {
  access_log off;
  error_log /dev/stdout warn;

  # dtable-server 1
  upstream dtable_server_a_z {
    server dtable-server:5000;
    keepalive 15;
  }

  # dtable-server 2
  upstream dtable_server_0_9 {
    server dtable-server-2:5000;
    keepalive 15;
  }

  # Map to dynamically determine the upstream server based on the UUID in the URL
  map $request_uri $dtable_upstream {
    default                                  dtable_server_a_z;    # Default to the a-z server
    "~*ff84e1a1-66e2"                        dtable_server_0_9;    # force this base to server 2
    "~*([a-zA-Z])([0-9a-f]{7}-[0-9a-f]{4})"  dtable_server_a_z;
    "~*([0-9])([0-9a-f]{7}-[0-9a-f]{4})"     dtable_server_0_9;
  }

  server {
    server_name _;
    listen 5000;

    location / {
      proxy_pass http://$dtable_upstream;
      proxy_set_header X-Upstream-Server $dtable_upstream;
      client_max_body_size 100m;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection upgrade;
      access_log /tmp/access.log;
      error_log /tmp/error.log;
    }
  }
}

{
    # Enable metrics
    metrics
}

:5000 {
        # Use route to disable internal reordering of directives
        route {
                metrics /metrics

                # Static paths are proxied to dtable-server:5000
                @staticPaths {
                        path /ping/ /api/v1/admin/sys-info/
                }
                reverse_proxy @staticPaths dtable-server:5000

                request_body {
                        max_size 100MB
                }

                # We cannot use Caddy's path_regexp matcher since this does not check query parameters
                # However, clients connect to dtable-server using /socket.io?dtable_uuid=<UUID> so
                # we rely on Caddy's CEL (Common Expression Language) instead to match against the full URI
                @dtable_09 `{http.request.orig_uri}.matches('[0-9][0-9a-f]{7}-[0-9a-f]{4}')`
                @dtable_az `{http.request.orig_uri}.matches('[a-zA-Z][0-9a-f]{7}-[0-9a-f]{4}')`

                reverse_proxy @dtable_az dtable-server:5000
                reverse_proxy @dtable_09 dtable-server-2:5000

                # Respond with 404 if nothing matches
                respond 404
        }
}