moonraker/docs/installation.md

Installation

This document provides a guide on how to install Moonraker on a Raspberry Pi running Raspian/Rasperry Pi OS. Other SBCs and/or linux distributions may work, however they may need a custom install script. Moonraker requires Python 3.7 or greater, verify that your distribution's Python 3 packages meet this requirement.

Klipper should be installed prior to installing Moonraker. Please see Klipper's Documention for instructions on how to do this.

After Klipper is installed, you need to modify its "default" file. This file contains klipper's command line arguments, and you must add an argument that instructs Klippy to create a Unix Domain socket:

sudo nano /etc/default/klipper

You should see a file that looks something like the following:

# Configuration for /etc/init.d/klipper

KLIPPY_USER=pi

KLIPPY_EXEC=/home/pi/klippy-env/bin/python

KLIPPY_ARGS="/home/pi/klipper/klippy/klippy.py /home/pi/printer.cfg -l /tmp/klippy.log"

You need to add -a /tmp/klippy_uds to KLIPPY_ARGS:

# Configuration for /etc/init.d/klipper

KLIPPY_USER=pi

KLIPPY_EXEC=/home/pi/klippy-env/bin/python

KLIPPY_ARGS="/home/pi/klipper/klippy/klippy.py /home/pi/printer.cfg -l /tmp/klippy.log -a /tmp/klippy_uds"

You may also want to take this opportunity to change the location of printer.cfg if you enable Moonraker's "config_path" option (see the configuration section for more information).

You can now install the Moonraker application:

cd ~
git clone https://github.com/Arksine/moonraker.git

Finally, run moonraker's install script:

cd ~/moonraker/scripts
./install-moonraker.sh

The install script has a few command line options that may be useful, particularly for those upgrading:

• -r
  This will rebuild the virtual environment for existing installations. Sometimes this is necessary when a dependency has been added.
• -f
  This will tell the script to overwrite Moonraker's "defaults" file. By default the script will not modify the "defaults" file if it is detected as present.
• -c /path/to/moonraker.conf
  This allows the user to specify the path to Moonraker's config file. The default location is "/home//moonraker.conf".

When the script completes it should start both Moonraker and Klipper. In klippy.log you should find the following entry:
webhooks: New connection established

Now you may install a client, such as Mainsail.

• Note that as of the time of this writing (August 11 2020) the current version of Mainsail (0.1.2) is not compatible with this repo. Please give the developer some time to bring up Mainsail in line with the latest release of Moonraker.

Command line Usage

The configuration and log file paths may be specified via the command line.

usage: moonraker.py [-h] [-c <configfile>] [-l <logfile>]

Moonraker - Klipper API Server

optional arguments:
  -h, --help            show this help message and exit
  -c <configfile>, --configfile <configfile>
                        Location of moonraker configuration file
  -l <logfile>, --logfile <logfile>
                        log file name and location

The default configuration is:

• config file - ~/moonraker.conf
• log file - /tmp/moonraker.log

It is recommended to use the defaults, however one may change these arguments by editing /etc/default/moonraker.

Prerequisites (Klipper Configuration)

Moonraker depends on the following Klippy extras for full functionality:

• [virtual_sdcard]
• [pause_resume]
• [display_status]

If you have a filament_switch_sensor configured then pause_resume will automatically be loaded. Likewise, if you have a display configured then display_status will be automatically loaded. If your configuration is missing one or both, you can simply add the bare sections to printer.cfg:

[pause_resume]

[display_status]

[virtual_sdcard]
path: ~/gcode_files

NOTES:

• While Klipper does not set any hard limits on the location of the path option for the virtual_sdcard, Moonraker requires that the path be located within the HOME directory, it cannot however be the HOME directory. If you wish to host your files elsewhere, use a symlink.
• Upon first starting Moonraker is not aware of the gcode file path, thus it cannot serve gcode files, add directories, etc. After Klippy enters the "ready" state it sends Moonraker the gcode file path. Once Moonraker receives the path it will retain it regardless of Klippy's state, and update it if the path is changed in printer.cfg.

Please see configuration.md for details on how to configure moonraker.conf.