A community based topic aggregation platform built on atproto

fix: modifying caddyfile for automatic websocket handling

+3 -3
Caddyfile
···
health_timeout 5s
# Headers for proper client IP handling
header_up X-Real-IP {remote_host}
header_up X-Forwarded-For {remote_host}
header_up X-Forwarded-Proto {scheme}
-
# WebSocket support for firehose
-
header_up Connection {>Connection}
-
header_up Upgrade {>Upgrade}
}
# Logging (Docker captures stdout/stderr)
···
health_timeout 5s
# Headers for proper client IP handling
+
header_up Host {host}
header_up X-Real-IP {remote_host}
header_up X-Forwarded-For {remote_host}
header_up X-Forwarded-Proto {scheme}
+
# Note: Caddy v2 handles WebSocket upgrades automatically
+
# No need for explicit Connection/Upgrade headers
}
# Logging (Docker captures stdout/stderr)
+1
docker-compose.prod.yml
···
PDS_PORT: 3000
PDS_DATA_DIRECTORY: /pds
PDS_BLOBSTORE_DISK_LOCATION: /pds/blocks
# PLC Directory (production)
PDS_DID_PLC_URL: https://plc.directory
···
PDS_PORT: 3000
PDS_DATA_DIRECTORY: /pds
PDS_BLOBSTORE_DISK_LOCATION: /pds/blocks
+
PDS_BLOB_UPLOAD_LIMIT: 104857600 # 100 MB
# PLC Directory (production)
PDS_DID_PLC_URL: https://plc.directory