homer/dummy-data
2022-12-20 20:27:13 +01:00
..
octoprint/api Octoprint service (#324) (#560) 2022-11-27 09:41:12 -08:00
openweather Shorter weather title 2022-10-30 15:13:59 +01:00
pihole Improve demo content 2022-10-11 13:57:42 +02:00
proxmox/api2/json/nodes/node1 Add missing data for proxmox demo 2022-12-07 22:48:38 +01:00
qBittorrent/api/v2 qBittorrent service (#540) 2022-10-30 10:32:51 -07:00
rtorrent Service for rTorrent. (#511) 2022-10-31 02:09:59 -07:00
speedtesttracker/api/speedtest Octoprint service (#324) (#560) 2022-11-27 09:41:12 -08:00
_headers Fix typo in demo page (#574) 2022-12-20 20:27:13 +01:00
README.md Octoprint service (#324) (#560) 2022-11-27 09:41:12 -08:00

Dummy data

This directory content makes possible to test custom services cards or create a demo without actually running the service. The principle is simple: save a sample output of the API used in the service in a static file in this directory. The path must be identical as the service endpoint to be used seamlessly.

Start the mock server to expose dummy data

yarn mock

How to add a new services sample

  • create a directory for your service, and any sub-folder existing in the service api path.
  • save the api output in a file named after the service endpoint.

Example:

mkdir pihole
curl http://my-pihole.me/admin/api.php -o pihole/api.php # /admin is omited because for PiHole, the implementation expect it to be in the base url (`url` or `endpoint` property)