fix: use websecure + tls for lidm routes, same pattern as other services

Cloudflare Origin CA wildcard cert covers *.asepharyana.my.id,
so websecure entrypoint with tls works correctly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
asepharyana
2026-07-23 19:07:22 +07:00
co-authored by Claude Opus 4.8
parent 7fc863d611
commit 478a0f849f
+15 -16
View File
@@ -30,22 +30,6 @@ http:
- common-chain@file
service: jaeger-service
services:
hub-service:
loadBalancer:
servers:
- url: 'http://hub:3000'
scraper-service:
loadBalancer:
servers:
- url: 'http://scraper-api:4091'
jaeger-service:
loadBalancer:
servers:
- url: 'http://jaeger:16686'
# ── LSAR Frontend ──
lidm-frontend:
rule: 'Host(`lidm.asepharyana.my.id`)'
@@ -67,6 +51,21 @@ http:
service: lidm-backend-service
services:
hub-service:
loadBalancer:
servers:
- url: 'http://hub:3000'
scraper-service:
loadBalancer:
servers:
- url: 'http://scraper-api:4091'
jaeger-service:
loadBalancer:
servers:
- url: 'http://jaeger:16686'
lidm-frontend-service:
loadBalancer:
servers: