Asynchronous HTTP Retriever
Service for retrieving HTTP resources asynchronously. Self-hosted within a lovely collection of docker containers.
POST request containing
callback and (optionally)
header values. Content for the given
url will be retrieved eventually and sent in a
POST request to the specified
docker-compose present on the host you want to run this on.
Developed and tested against
docker 18.06.1-ce and
- Documentation home
- Getting started
- Request-Response Cycle
- Requesting a Resource
- Callback Responses
Reporting An Issue, Creating a Feature Request
Report a bug/issue/fault if something does not work the way it should.
Create a feature request if something new is needed.
Feel free to fork and make whatever changes you like.
Create a Development Installation
To run a development copy:
Branch from master
Always branch from
Append the issue number to the branch name.
To run the full test suite, refer to the travis-ci build script
Run the full test suite in the same manner as the travis-ci build.
To execute an individual test or set of tests from your host:
cd docker docker-compose exec -T --env APP_ENV=test app-web \ ./vendor/bin/phpunit tests/<path to test class>
To execute an individual test or set of tests from within your container:
cd docker docker-compose exec app-web /bin/bash APP_ENV=test ./vendor/bin/phpunit tests/<path to test class>
Ensure your development environment database is empty before running functional tests.
Creating Pull Requests
Create pull requests against
A pull request must always reference an existing issue. The issue serves to document the matter being addressed.
Pull requests that change functionality must include new or updated tests that demonstrate the correctness of the change.
Always run the full test suite locally before creating a pull request. Address any issues that arise before creating a pull request.