Monorepo for Aesthetic.Computer
aesthetic.computer
lith Caddy: serve prompt.ac/menuband without redirect
Path-specific exception inside the @promptac handle: /menuband* serves
the static files from /opt/ac/system/public directly, so the menuband
landing page renders under either prompt.ac or aesthetic.computer.
Everything else under prompt.ac still 301s to aesthetic.computer.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
+16
-8
+16
-8
lith/Caddyfile
+16
-8
lith/Caddyfile
···
388
388
redir https://aesthetic.computer{uri} 301
389
389
}
390
390
391
-
# --- prompt.ac → aesthetic.computer (301 redirect) ---
392
-
# /menuband is served directly (no redirect) so the landing page
393
-
# works under either domain. Everything else still bounces.
391
+
# --- prompt.ac/menuband: serve from origin (no redirect) ---
392
+
# The host+path matcher is more specific than the host-only @promptac
393
+
# below, so Caddy evaluates this first. Earlier nested-handle attempt
394
+
# silently fell through to the redirect; named top-level matchers are
395
+
# the reliable shape.
396
+
@promptac_menuband {
397
+
host prompt.ac
398
+
path /menuband /menuband/*
399
+
}
400
+
handle @promptac_menuband {
401
+
root * /opt/ac/system/public
402
+
try_files {path} {path}/index.html
403
+
file_server
404
+
}
405
+
406
+
# --- prompt.ac → aesthetic.computer (everything else, 301) ---
394
407
@promptac host prompt.ac
395
408
handle @promptac {
396
-
handle /menuband* {
397
-
root * /opt/ac/system/public
398
-
try_files {path} {path}/index.html
399
-
file_server
400
-
}
401
409
redir https://aesthetic.computer{uri} 301
402
410
}
403
411