@@ -7,14 +7,15 @@ reverse-proxy (in `reverse_proxy/`), and a PostgreSQL database (in `db/`).
77We provide configurations to run it using either Docker Compose or Kubernetes.
88The Docker Compose version is simpler and easier if you just want to get
99started with as few dependencies as possible; the Kubernetes version may be
10- useful for users already using Kubernetes for other deployments.
10+ useful for users who are either already using Kubernetes for other deployments
11+ or require elastic horizontal scaling of their Skip service.
1112
1213## Docker Compose  
1314
1415To build and run the application using Docker Compose, first install and run
1516Docker on your system, then run:
1617
17- ``` 
18+ ``` bash 
1819$ docker compose up --build
1920``` 
2021
@@ -26,7 +27,7 @@ of computing and maintaining resources in a round-robin fashion.
2627
2728This distributed configuration requires only configuration changes, is
2829transparent to clients, and can be run with:
29- ``` 
30+ ``` bash 
3031$ docker compose -f compose.distributed.yml up --build
3132``` 
3233
@@ -50,7 +51,7 @@ configuration) to a local Kubernetes cluster.
5051
51523 .  Build docker images for each component of this example, then tag and publish
5253   each one to the ` minikube `  registry:
53- ``` 
54+ ``` bash 
5455docker compose -f kubernetes/compose.distributed.yml build
5556for  image  in  web-service reactive-service www db ;  do 
5657  docker tag reactive-hackernews/$image  localhost:5000/$image ; 
63645 .  Configure and run HAProxy as a Kubernetes ingress controller, mediating
6465   external traffic ("ingress") and distributing it to the relevant Kubernetes
6566   service(s).
66- ``` 
67+ ``` bash 
6768kubectl create configmap haproxy-auxiliary-configmap --from-file kubernetes/haproxy-aux.cfg
6869helm install haproxy haproxytech/kubernetes-ingress -f reverse_proxy/kubernetes.yaml
6970``` 
0 commit comments