9da74f7bc6
Rather than tracking watch paths directly, wrap each watch in a node. This makes makes it a bit easier to handle move and delete changes, as we don't have to manage several different dicts to store the information we need. Signed-off-by: Eric Callahan <arksine.code@gmail.com> |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| moonraker | ||
| scripts | ||
| test/client | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .readthedocs.yaml | ||
| LICENSE | ||
| README.md | ||
| mkdocs.yml | ||
README.md
Moonraker - API Web Server for Klipper
Moonraker is a Python 3 based web server that exposes APIs with which client applications may use to interact with Klipper. Communcation between the Klippy host and Moonraker is done over a Unix Domain Socket. Tornado is used to provide Moonraker's server functionality.
Documentation for users and developers can be found on Read the Docs.
Note that Moonraker does not come bundled with a client, you will need to install one. The following clients are currently available:
- Mainsail by Meteyou
- Fluidd by Cadriel
- KlipperScreen by jordanruthe
- mooncord by eliteSchwein
Changes
This section contains changelogs that users and developers may reference to see if any action is necessary on their part. The date of the most recent change is included.
Users:
user_changes.md - April 19th 2021
Developers:
api_changes.md - March 15th 2021