From 6cb039f0251f8c4fca4af095bb8fd061a5976e11 Mon Sep 17 00:00:00 2001 From: Yousaf Nabi Date: Fri, 6 Sep 2024 14:09:49 +0100 Subject: [PATCH] docs: remove dius pact broker section DiUS pact broker image is no longer supported and is not actively maintained. See https://github.com/pact-foundation/docs.pact.io/issues/242 --- README.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/README.md b/README.md index 902e846..f11b0b1 100644 --- a/README.md +++ b/README.md @@ -27,12 +27,6 @@ The `pactfoundation/pact-broker` image is a forked version of the `dius/pact-bro All the environment variables used for `dius/pact-broker` are compatible with `pactfoundation/pact-broker`. The only breaking change is that the default port has changed from `80` to `9292` (because a user without root permisisons cannot bind to a port under 1024). If you wish to expose port 80 (or 443) you can deploy Ngnix in front of it (see the [docker-compose](https://github.com/pact-foundation/pact-broker-docker/blob/master/docker-compose.yml) file for an example). -### Which one should I use? - -Please read https://github.com/phusion/passenger/wiki/Puma-vs-Phusion-Passenger for information on which server will suit your needs best. The tl;dr is that if you want to run the docker image in a managed architecture which will make your application highly available (eg. ECS, Kubernetes) then use the `pactfoundation/pact-broker`. Puma will not restart itself if it crashes, so you will need external monitoring to ensure the Pact Broker stays available. - -If you want to run the container as a standalone instance, then the `dius/pact-broker` image which uses Phusion Passenger may serve you better, as Passenger will restart any crashed processes. - ## Platforms Multi-platform images are available