Newer
Older
jeltz-klipper-config / moonraker.conf
[server]
host: 0.0.0.0
port: 7125
klippy_uds_address: /home/cory/printer_data/comms/klippy.sock

[authorization]
trusted_clients:
    10.42.0.0/16
    10.0.0.0/8
    127.0.0.0/8
    169.254.0.0/16
    172.16.0.0/12
    192.168.0.0/16
    FE80::/10
    ::1/128
cors_domains:
    *.lan
    *.local
    *.internal
    *://localhost
    *://localhost:*
    *://my.mainsail.xyz
    *://app.fluidd.xyz

[notifier discord_klipping]
url: https://discordapp.com/api/webhooks/{secrets.discord_webhook.id}/{secrets.discord_webhook.token}
events: started, complete, error, cancelled, paused, resumed
#   The events this notifier should trigger to. '*' means all events.
#   You can use multiple events, comma separated.
#   Valid events:
#      started
#      complete
#      error
#      cancelled
#      paused
#      resumed
#   This parameter must be provided.
body: "Your printer status has changed to {event_name}"
#   The body of the notification. This option accepts Jinja2 templates, where
#   the template is passed a context containing the following fields:
#      event_name: The name of the event that triggered the notification
#                  (ie: started, complete, error, etc)
#      event_args: A list containing the arguments passed to the event.
#                  See the "Tip" below for additional details on this field.
#      event_message: An additional message passed to the notification when
#                     triggered.  This is commonly used when the notification
#                     is received from Klippy using a gcode_macro.
#   The default is a body containing the "name" of the notification as entered
#   in the section header.
# body_format:
# #   The formatting to use for the body, can be `text`, `html` and `markdown`.
# #   The default is `text`.
# title:
# #   The optional title of the notification. This option accepts Jinja2 templates,
# #   the template will receive a context with the same fields as the body.  The
# #   default is an empty string as the title.
# attach:
# #   One or more items to attach to the notification. This may be a path to a
# #   local file or a url (such as a webcam snapshot).  Multiple attachments must be
# #   separated by a newline.  This option accepts Jinja2 templates, the template
# #   will receive the same context as the "body" and "title" options.  The default
# #   is no attachment will be sent with the notification.
# #
# #   Note: Attachments are not available for all notification services, you can
# #   check if it's supported on the Apprise Wiki.  Be aware that links to items
# #   hosted on your local network can only be viewed within that network.

[octoprint_compat]

[history]

[update_manager]
channel: dev
refresh_interval: 168

[update_manager mainsail-config]
type: git_repo
primary_branch: master
path: ~/mainsail-config
origin: https://github.com/mainsail-crew/mainsail-config.git
managed_services: klipper

[update_manager mainsail]
type: web
channel: stable
repo: mainsail-crew/mainsail
path: ~/mainsail


[update_manager led_effect]
type: git_repo
path: ~/klipper-led_effect
origin: https://github.com/julianschill/klipper-led_effect.git
is_system_service: False


[update_manager client Filaments]
type: git_repo
path: ~/filaments-klipper-extra
primary_branch: mainline
origin: https://github.com/garethky/filaments-klipper-extra.git
install_script: install.sh
managed_services: klipper

# Crowsnest update_manager entry
[update_manager crowsnest]
type: git_repo
path: ~/crowsnest
origin: https://github.com/mainsail-crew/crowsnest.git
managed_services: crowsnest
install_script: tools/pkglist.sh

[include octoeverywhere-system.cfg]

[update_manager mobileraker]
type: git_repo
path: /home/cory/mobileraker_companion
origin: https://github.com/Clon1998/mobileraker_companion.git
primary_branch:main
managed_services: mobileraker
env: /home/cory/mobileraker-env/bin/python
requirements: scripts/mobileraker-requirements.txt
install_script: scripts/install.sh