homelab-codex-ws/services/kb-site/docker-compose.yml
oskar 19548d888e fix(kb-site): wycofaj robots.txt — blokowal legalny fetch z tokenem
"User-agent: * / Disallow: /" odbijalo nie tylko wyszukiwarki, ale kazdego
klienta respektujacego robots.txt (m.in. fetch asystentow AI) — takze takiego,
ktory znal token dostepu. Token mial WPUSZCZAC znajacych go, a robots.txt ich
WYPYCHAL.

Dzialalo tez przeciwko wlasnemu celowi: crawler zablokowany przed pobraniem
strony nigdy nie widzi meta noindex, a wyszukiwarka i tak potrafi wylistowac
sam URL, ktorego nie wolno jej bylo pobrac.

Ochrona przed indeksowaniem zostaje bez zmian: <meta name="robots"
content="noindex, nofollow"> w <head> kazdej strony (scripts/kb/gen_pages.py).

Plik mial jedna linie polityki, wiec bez niej tracil sens — usuniety razem
z bind-mountem w compose (katalog static/ zniknal jako pusty).

Test: docker compose config (exit 0, zostaje tylko named volume);
gen_pages.py --check — CZYSTO, 0 trafien.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-05 13:11:43 +02:00

51 lines
2.3 KiB
YAML

services:
kb-site:
image: nginx:alpine
container_name: kb-site
restart: unless-stopped
ports:
# PIHA 82x0 static-HTTP block: 8210 paperless, 8220 nextcloud,
# 8230 kb-query, 8240 narty27 -> 8250 is the next free slot.
# Publicly the site is reached only through the npm@PIHA vhost
# kb-e2a24af3.okit.pl; this bind is the proxy's upstream.
- "8250:80"
volumes:
# Generated output of scripts/kb/gen_pages.py — never committed, never
# bind-mounted from the repo. Read-only: nginx only serves it; writes go
# through the helper-container procedure in kb/runbooks/kb-site-deploy.md
# (docker cp cannot write into a :ro mount).
- kb-site_content:/usr/share/nginx/html:ro
# Celowo brak mounta robots.txt: "Disallow: /" blokował nie tylko
# wyszukiwarki, ale każdy klient respektujący robots.txt (m.in. fetch
# asystentów AI) — także ten, który znał token dostępu. Za ochronę przed
# indeksowaniem odpowiada `noindex, nofollow` w <head> każdej strony
# (scripts/kb/gen_pages.py).
# Docker on PIHA has exhausted its default address pools (~30 live stacks:
# "all predefined address pools have been fully subnetted"), so this stack
# must not ask for a subnet of its own. Declaring a network here suppresses
# the implicit kb-site_default; we join the pre-existing shared "proxy"
# bridge instead. This is only about subnet economy — npm@PIHA still reaches
# this container over the published 8250 host port (npm itself lives on
# nginxproxymanager_default), not over this network.
networks:
- proxy
# busybox wget — nginx:alpine ships no curl. index.html is generated on
# every run, so it is the one file that must always be there.
healthcheck:
test: ["CMD", "wget", "-q", "-O", "/dev/null", "http://127.0.0.1/index.html"]
interval: 30s
timeout: 10s
retries: 5
start_period: 5s
networks:
# Created out-of-band on PIHA (docker network create proxy); never managed by
# this stack. `docker network ls | grep -w proxy` must return a row before
# deploy, otherwise compose fails with "network proxy declared as external,
# but could not be found".
proxy:
external: true
volumes:
kb-site_content: