The self-hosted HTTP mock service typically exposes a set of endpoints that you can configure to return pre-defined responses, such as HTTP status codes, headers, and message bodies. You can use the mock service to test different scenarios, such as error responses, timeouts, or unexpected input, to ensure that your application can handle these situations correctly.
Run with docker:
sudo docker run -v /var/mock:/var/mock/ -p 8111:8111 dhnikolas/mock:latest
Usage with application UI:
http://localhost:8111/ui/
Configure endpoints:
Make request and get response:
$ curl http:/localhost:8111/api/v1/pam
{"project_id": "s98fsufhs9fusnf9si"}
Show request logs:
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature - Commit your changes:
git commit -am 'Add some feature' - Push to the branch:
git push origin my-new-feature - Submit a pull request :D
Lead Developer - Nikolai (@dhnikolas)
The MIT License (MIT)
Copyright (c) 2023 Nikolai
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.