thinking of using something like this for exporting to a grafana dashboard, not sure if it would be better to have a base image with only PyP100 and another that adds flask and the example script
ps: probably good to remove ==0.0.18 once #62 is fixed
ps2: a github action to build the image might be nice too
ps3: usage:
$ docker build . -t tapo
$ docker run -it --rm \
-e IP_ADDRESS=192.168.1.420 \
-e EMAIL=some@mail.com \
-e PASSWORD=some_secret \
-v "$(pwd)/examples/P110.py:/P110.py" \
-p 5000:5000 \
tapo \
python3 P110.py
* Serving Flask app 'P110' (lazy loading)
* Environment: development
* Debug mode: off
* Running on all addresses (0.0.0.0)
WARNING: This is a development server. Do not use it in a production deployment.
* Running on http://127.0.0.1:5000
* Running on http://172.17.0.2:5000 (Press CTRL+C to quit)
172.17.0.1 - - [24/Apr/2022 19:29:05] "GET /info HTTP/1.1" 200 -
172.17.0.1 - - [24/Apr/2022 19:31:58] "GET /usage HTTP/1.1" 200 -
ps4: could probably create this as a separate exporter-like repo instead of here
Hi,
I'm not sure wether this fits within this repo by itself. Could you put it into its own repo and then I could add some sort of an examples section to the readme that can link to it and others if there are any?
thinking of using something like this for exporting to a grafana dashboard, not sure if it would be better to have a base image with only PyP100 and another that adds flask and the example script
ps: probably good to remove
==0.0.18
once #62 is fixed ps2: a github action to build the image might be nice too ps3: usage:ps4: could probably create this as a separate exporter-like repo instead of here