Quibble defaults to the PHP built-in server, but since release 0.0.46 also includes Apache support. The quibble-apache:0.0.1 image includes the necessary packages.
In this task, we'll create a few non-voting jobs in various repos, which exercise quibble+apache. We want to determine:
- How does performance compare to the regular quibble job?
- Do some repos have quirks to address before we can use the apache job?
See this example job which includes the necessary glue. Hopefully this can be simplified a bit.
The major difference is that the apache job can serve requests concurrently, which will expose some issues with our code and require fixes to stabilize tests.
In the long-term, if the results are encouraging we might decide to switch all quibble jobs to use apache.