Support TLS "ingress" in docker compose #933

Open
opened 2024-08-21 04:23:55 +00:00 by dboreham · 2 comments
Owner
No description provided.
Author
Owner

Based on caddy

Based on caddy
Author
Owner

One use case for this is where a laconicd stack is deployed in compose, then someone wants to host the block explorer as a webapp in k8s, pointing at that laconicd as its back end. This won't work as-is because modern browsers don't allow a page loaded with TLS to access non-TLS rpc services.

One use case for this is where a laconicd stack is deployed in compose, then someone wants to host the block explorer as a webapp in k8s, pointing at that laconicd as its back end. This won't work as-is because modern browsers don't allow a page loaded with TLS to access non-TLS rpc services.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#933
No description provided.