Web app to integrate with and extend farmOS
Lance Edgar
cc4b94a7b8
in some cases (maybe just dev?) the record does not exist in farmOS; if so we should silently ignore. and there seemed to be a problem with the sequence of events: - user clicks delete in WF - record is deleted from WF DB - delete request sent to farmOS API - webhook on farmOS side calls back to WF webhook URI somewhere in there, in practice things seemed to hang after user clicks delete. i suppose the thread handling user's request is "tied up" somehow, such that the webhook receiver can't process that request? that doesn't exactly make sense to me, but if we split off to a separate thread to request the farmOS deletion, things seem to work okay. so maybe that idea is more accurate than i'd expect |
||
|---|---|---|
| docs | ||
| src/wuttafarm | ||
| style | ||
| .gitignore | ||
| CHANGELOG.md | ||
| COPYING.txt | ||
| pyproject.toml | ||
| README.md | ||
| tasks.py | ||
| tox.ini | ||
WuttaFarm
This is a Python web app (built with WuttaWeb), to integrate with and extend farmOS.
It is just an experiment so far; the ideas I hope to play with include:
- display farmOS data directly, via real-time API fetch
- add "mirror" schema and sync data from farmOS to app DB (and display it)
- possibly add more schema / extra features
- possibly sync data back to farmOS
See full docs at https://docs.wuttaproject.org/wuttafarm/