6e6388d673
Previously the Klipper repo location can be changed outside of the lock. If the location of the Klipper path is moved while an autorefresh is occurring it is possible for Moonraker to call refresh and/or notify_update_refreshed before the repo has been initialized. This commit moves the re-assignment of the "klipper" updated inside the lock. In addition AppDeploy._is_valid is now defined in the __init__() method. Signed-off-by: Eric Callahan <arksine.code@gmail.com> |
||
---|---|---|
.github | ||
docs | ||
moonraker | ||
scripts | ||
tests | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.readthedocs.yaml | ||
LICENSE | ||
README.md | ||
mkdocs.yml | ||
pdm.lock | ||
pyproject.toml | ||
pytest.ini |
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 the 3D printing firmware Klipper. Communication 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.
Clients
Note that Moonraker does not come bundled with a client, you will need to install one. The following clients are currently available:
- Mainsail by Mainsail-Crew
- Fluidd by Cadriel
- KlipperScreen by jordanruthe
- mooncord by eliteSchwein
Raspberry Pi Images
Moonraker is available pre-installed with the following Raspberry Pi images:
- MainsailOS by Mainsail-Crew
- Includes Klipper, Moonraker, and Mainsail
- FluiddPi by Cadriel
- Includes Klipper, Moonraker, and Fluidd
Docker Containers
The following projects deploy Moonraker via Docker:
- prind by mkuf
- A suite of containers which allow you to run Klipper in Docker. Includes support for OctoPrint and Moonraker.
Changes
Please refer to the changelog for a list of notable changes to Moonraker.