A smaller and sexier Docker image has now been built in the Pact Foundation organization. The new image can be run without root permissions, and is only 98MB compressed! All environment variable configurations are the same, so you should just be able to switch from
pactfoundation/pact-brokerand run with it - note that the default port has changed from 80 to 9292 though.
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.
Note: On 12 May 2018, the format of the docker tag changed from
M.m.pis the semantic version of the underlying Pact Broker package) so that Dependabot can recognise when the version has been incremented.
In a hurry?
If you want to try out a Pact Broker that can be accessed by all your teams, without having to fill in requisition forms and wait for 3 months, you can get a free trial at pactflow.io. Built by a group of core Pact maintainers, Pactflow is a fork of the OSS Pact Broker with extra goodies like an improved UI, field level verification results and federated login. It's also fully supported, and that means when something goes wrong, someone else gets woken up in the middle of the afternoon to fix it...
- A running postgresql database and the ability to connect to it (see POSTGRESQL.md).
- If on Mac, you will need the
gtimeoutfunction. You can install
brew install coreutils.
- Install Docker
- Prepare your environment if you are not running postgresql in a docker container. Setup the pact broker connection to the database through the use of the following environment variables. If you want to use a disposable postgres docker container just do
export DISPOSABLE_PSQL=truebefore running the script/test.sh.
For a postgres or mysql database:
You can either set the
PACT_BROKER_DATABASE_URL in the format
postgres://user1:pass1@myhost/mydb) or, you can set the credentials individually using the following environment variables:
Adapter can be 'postgres' (recommended) or 'mysql2' (please note that future JSON search features may not be supported on mysql). SQLite will work for spikes, but it is NOT supported as a production database.
For an SQLite database (only recommended for investigation/spikes, as it will be disposed of with the container unless you mount it from an external file system):
PACT_BROKER_DATABASE_ADAPTER(set to 'sqlite')
PACT_BROKER_DATABASE_NAME(arbitrary name eg. /tmp/pact_broker.sqlite)
You can additionally set:
-p 80:80to start the docker image, as some of the Rack middleware gets confused by receiving requests for other ports and will return a 404 otherwise (port forwarding does not rewrite headers).
- On OSX, if you are not using Docker native, use
docker-machine ip $(docker-machine active)to get the IP of the VirtualBox, and connect on port 80.
- The application makes use of the phusion passenger application server.
- Apart from creating a database no further preparation is required.
Using basic auth
To enable basic auth, run your container with:
If you want to allow public read access (but still require credentials for writing), then omit setting the READ_ONLY credentials and set
Developers should use the read only credentials on their local machines, and the CI should use the read/write credentials. This will ensure that pacts and verification results are only published from your CI.
Note that the verification status badges are not protected by basic auth, so that you may embed them in README markdown.
If you are using the docker container within an AWS autoscaling group, and you need to make a heartbeat URL publicly available, set
PACT_BROKER_PUBLIC_HEARTBEAT=true. No database connection will be made during the execution of this endpoint.
Setting the log level
Set the environment variable
PACT_BROKER_LOG_LEVEL to one of
- PACT_BROKER_WEBHOOK_HOST_WHITELIST - a space delimited list of hosts (eg.
github.com), network ranges (eg.
10.2.3.41/24, or regular expressions (eg.
/.*\\.foo\\.com$/). Regular expressions should start and end with a
/to differentiate them from Strings. Note that backslashes need to be escaped with a second backslash. Please read the Webhook whitelists section of the Pact Broker configuration documentation to understand how the whitelist is used. Remember to use quotes around this value as it may have spaces in it.
- PACT_BROKER_WEBHOOK_SCHEME_WHITELIST - a space delimited list (eg.
http https). Defaults to
Other environment variables
- PACT_BROKER_BASE_URL - optional. If you find that the URLs generated by the API are using an IP instead of a hostname, you can set this environment variable to force the desired base URL. Must include the port if it's a non-standard one. eg.
https://my-broker:9292. Is not currently used for links in the UI.
- PACT_BROKER_BASE_EQUALITY_ONLY_ON_CONTENT_THAT_AFFECTS_VERIFICATION_RESULTS -
trueby default, may be set to
- PACT_BROKER_ORDER_VERSIONS_BY_DATE -
trueby default. Setting this to false is deprecated.
- PACT_BROKER_DISABLE_SSL_VERIFICATION -
falseby default, may be set to
true. Disables SSL verification for webhook endpoints.
General Pact Broker configuration and usage
Documentation for the Pact Broker application itself can be found in the Pact Broker docs.
Running with Docker Compose
For a quick start with the Pact Broker and Postgres, we have an example Docker Compose setup you can use:
- Modify the
docker-compose.ymlfile as required.
docker-compose upto get a running Pact Broker and a clean Postgres database
Now you can access your local broker:
NOTE: this image should be modified before using in Production, in particular, the use of hard-coded credentials
Running with Openshift
See pact-broker-openshift for an example config file.
See the Troubleshooting page on the wiki.