Skip to content

Commit

Permalink
docs: remove dius pact broker section
Browse files Browse the repository at this point in the history
DiUS pact broker image is no longer supported and is not actively maintained.

See pact-foundation/docs.pact.io#242
  • Loading branch information
YOU54F authored Sep 6, 2024
1 parent 8d8f264 commit 6cb039f
Showing 1 changed file with 0 additions and 6 deletions.
6 changes: 0 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 6cb039f

Please sign in to comment.