Create a template reverse proxy container to compliment any web facing services. #6

New issue

Closed

opened 2018-10-06 18:28:54 +02:00 by Leopere · 1 comment

Leopere commented

2018-10-06 18:28:54 +02:00

(Migrated from github.com)

This container definition will be exclusively a docker-compose.yml as the official Docker library container for Traefik is all we need here.

Select the smallest and latest.

Set networking up so that other containers can connect to and from the reverse proxy.

Expose port 80/http and have it automagically redirect to 443.

Expose port 443/https and have it automagically provision LetsEncrypt certificates that are defined in container labels provided by any other containers in this LBRY container cluster with auto-discovery enabled.

The goal is a single docker host however it wouldn't take much to go the route of expanding to support Docker Swarm, Rancher OS, and Kubernetes which I think are the only relevant targets at first. I plan to keep this as simple as possible at first so that we can cover most if not all of the LBRY appliances and then we can add more features.

This container definition will be exclusively a docker-compose.yml as the official Docker library container for Traefik is all we need here. Select the smallest and latest. Set networking up so that other containers can connect to and from the reverse proxy. Expose port 80/http and have it automagically redirect to 443. Expose port 443/https and have it automagically provision LetsEncrypt certificates that are defined in container labels provided by any other containers in this LBRY container cluster with auto-discovery enabled. The goal is a single docker host however it wouldn't take much to go the route of expanding to support Docker Swarm, Rancher OS, and Kubernetes which I think are the only relevant targets at first. I plan to keep this as simple as possible at first so that we can cover most if not all of the LBRY appliances and then we can add more features.

Leopere commented

2018-10-07 03:50:34 +02:00

(Migrated from github.com)

This is completed and ready. The network-up.sh file has the command containing the external network that is required to operate this correctly.

No milestone

No project

No assignees

1 participant

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: LBRYCommunity/lbry-docker#6

No description provided.