Nick Craig-Wood 8dc4c01209 build: make integration tests run better on macOS and Windows
This changes as many of the integraton tests as possible so that they
use port forwarding rather than the docker IP directly.

Using the docker IP directly does not work on macOS and Windows as the
docker images are running in a VM rather than a container.

This adds the PORTS.md document to document which port numbers we are
using for which service as they need to be unique.
2024-04-16 10:48:48 +01:00
..
2024-03-10 11:22:43 +00:00
2023-03-25 09:34:10 +01:00

This directory contains scripts to start and stop servers for testing.

The commands are named after the remotes in use. They should be executable files with the following parameters:

start  - starts the server
stop   - stops the server
status - returns non-zero exit code if the server is not running

These will be called automatically by test_all if that remote is required.

When start is run it should output config parameters for that remote. If a _connect parameter is output then that will be used for a connection test. For example if _connect=127.0.0.1:80 then a TCP connection will be made to 127.0.0.1:80 and only when that succeeds will the test continue.

run.bash contains boilerplate to be included in a bash script for interpreting the command line parameters.

docker.bash contains library functions to help with docker implementations.

TODO