2026-10-09 21:29:59 +07:00
|
|
|
server {
|
|
|
|
|
listen 80;
|
|
|
|
|
listen [::]:80;
|
|
|
|
|
|
|
|
|
|
server_name _;
|
|
|
|
|
|
|
|
|
|
root /usr/share/nginx/html;
|
|
|
|
|
index index.html;
|
|
|
|
|
|
|
|
|
|
# React/Vue/Vite SPA routing
|
|
|
|
|
location / {
|
|
|
|
|
try_files $uri $uri/ /index.html;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
# Do not aggressively cache index.html.
|
|
|
|
|
# It references the latest hashed JS/CSS files.
|
|
|
|
|
location = /index.html {
|
|
|
|
|
try_files $uri =404;
|
|
|
|
|
|
|
|
|
|
add_header Cache-Control "no-cache, must-revalidate";
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
# Vite-generated assets normally contain content hashes.
|
|
|
|
|
# They can safely be cached for a long time.
|
|
|
|
|
location ~* \.(?:css|js|mjs|map|png|jpg|jpeg|gif|svg|ico|webp|avif|woff|woff2|ttf|otf)$ {
|
|
|
|
|
try_files $uri =404;
|
|
|
|
|
|
|
|
|
|
expires 30d;
|
|
|
|
|
add_header Cache-Control "public, max-age=2592000, immutable";
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
location = /favicon.ico {
|
|
|
|
|
access_log off;
|
|
|
|
|
log_not_found off;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
location = /robots.txt {
|
|
|
|
|
access_log off;
|
|
|
|
|
log_not_found off;
|
|
|
|
|
}
|
2026-10-22 09:55:21 +07:00
|
|
|
|
2026-10-26 20:49:34 +07:00
|
|
|
# Content write path (spec-v4 §6.2, spec-v4-deploy-infra D11/D13, spec-v6 D4):
|
|
|
|
|
# Basic-auth at the proxy; ${CONTENT_API_TOKEN} and ${CONTENT_API_BASE} are
|
|
|
|
|
# substituted by the image's envsubst template step from the container
|
|
|
|
|
# environment (sourced from the stack's secrets/site_config) BEFORE nginx parses
|
|
|
|
|
# this file — so proxy_pass below is a literal upstream once rendered, exactly as
|
|
|
|
|
# it was when the URL was written here. The SPA bundle and the repository never
|
|
|
|
|
# carry the token or the git host.
|
2026-10-22 09:55:21 +07:00
|
|
|
location /api/content/ {
|
|
|
|
|
auth_basic "Editor";
|
|
|
|
|
auth_basic_user_file /etc/nginx/htpasswd;
|
|
|
|
|
|
2026-10-26 20:49:34 +07:00
|
|
|
# HTTP/2 to the upstream (nginx >= 1.29.4; the stack runs 1.31.x; the API host
|
|
|
|
|
# answers an h2 ALPN handshake — verified against api.github.com 2026-10-26). The
|
|
|
|
|
# edit-mode client issues its 12 document reads + 2 label reads as one concurrent
|
|
|
|
|
# wave, so those requests multiplex over a single upstream connection instead of
|
|
|
|
|
# one HTTP/1.1 connection each. Upstream keepalive caching is already the default
|
|
|
|
|
# since 1.29.7; the docs still require the Connection header to be cleared for a
|
|
|
|
|
# reused upstream connection.
|
2026-10-26 21:46:13 +07:00
|
|
|
# rerun workflow
|
2026-10-24 14:45:26 +07:00
|
|
|
proxy_http_version 2;
|
|
|
|
|
proxy_set_header Connection "";
|
|
|
|
|
|
2026-10-26 20:49:34 +07:00
|
|
|
proxy_pass ${CONTENT_API_BASE};
|
2026-10-22 09:55:21 +07:00
|
|
|
proxy_ssl_server_name on;
|
2026-10-26 20:49:34 +07:00
|
|
|
# Bearer is the form the GitHub Contents API documents; the legacy "token"
|
|
|
|
|
# prefix was Gitea's.
|
|
|
|
|
proxy_set_header Authorization "Bearer ${CONTENT_API_TOKEN}";
|
2026-10-22 09:55:21 +07:00
|
|
|
}
|
2026-10-09 21:29:59 +07:00
|
|
|
}
|