mirror of
https://github.com/rgrgogu/new_starr.git
synced 2026-09-27 00:12:54 +08:00
kennethobsequio
c5699714dc
Our favorite hits aside from nginx conf Signed-off-by: Kenneth Obsequio <k80308392@gmail.com>
32 lines
1.2 KiB
Caddyfile
32 lines
1.2 KiB
Caddyfile
# Reverse proxy template for a REAL deployment (real domain + automatic HTTPS).
|
|
# Not needed for local testing against localhost:4650 — this is the step you
|
|
# take once you're actually putting this in front of a public domain.
|
|
#
|
|
# Usage:
|
|
# 1. Point 3 DNS records at this machine: your app domain, your api
|
|
# subdomain, and your cdn subdomain (matching FRONTEND_URL / APP_URL /
|
|
# S3_PUBLIC_URL in apps/api/.env and VITE_APP_URL / VITE_API_URL in
|
|
# apps/web/.env).
|
|
# 2. Install Caddy (https://caddyserver.com/docs/install) directly on this
|
|
# host — it is NOT part of docker-compose.yml, so it binds host ports
|
|
# 80/443 directly and reverse-proxies to the containers' published
|
|
# ports below.
|
|
# 3. Copy this file to /etc/caddy/Caddyfile (or wherever your install
|
|
# expects it), filling in the three domains.
|
|
# 4. sudo systemctl reload caddy (or: caddy run --config Caddyfile)
|
|
#
|
|
# Caddy issues and renews Let's Encrypt certificates automatically the first
|
|
# time each domain is requested — no manual cert steps needed.
|
|
|
|
yourdomain.com {
|
|
reverse_proxy localhost:4650
|
|
}
|
|
|
|
api.yourdomain.com {
|
|
reverse_proxy localhost:3024
|
|
}
|
|
|
|
cdn.yourdomain.com {
|
|
reverse_proxy localhost:3900
|
|
}
|