#OctoEverywhere made me dirty...

9 messages · Page 1 of 1 (latest)

hollow spindle
#

What is the correct way to resolve this...

pi@EnderRat:~ $ cd /home/pi/printer_data/config/RatOS; git status
On branch v2.x
Your branch is up to date with 'origin/v2.x'.

Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: moonraker.conf

Untracked files:
(use "git add <file>..." to include in what will be committed)
octoeverywhere-system.cfg
octoeverywhere.conf

no changes added to commit (use "git add" and/or "git commit -a")

pi@EnderRat:~/printer_data/config/RatOS $ git diff
diff --git a/moonraker.conf b/moonraker.conf
index 366c0fe..00923c7 100644
--- a/moonraker.conf
+++ b/moonraker.conf
@@ -85,3 +85,5 @@ install_script: scripts/KlipperScreen-install.sh

enables partial support of Octoprint API

[octoprint_compat]
+
+[include octoeverywhere-system.cfg]

torn marsh
#

Yeah octoeverywhere is modifying the wrong moonraker.conf. It's supposed to change /home/pi/printer_data/config/moonraker.conf. I don't know why it's doing a depth first search, but it's weird and buggy.

#

and

        octoeverywhere-system.cfg
        octoeverywhere.conf

Are supposed to go into /home/pi/printer_data/config

#

not RatOS.

#

This is a bug in the octoeverywhere script.

torn marsh
#

Hey, the installer should work now, can you give it a go?

hollow spindle
hollow spindle
#
  1. ssh to pi
  2. cd /home/pi/printer_data/config/RatOS
  3. git restore moonraker.conf
  4. rm octoeverywhere.conf
  5. rm octoeverywhere-system.cfg
  6. cd ~
  7. Ran the install script.
  8. Login to Octoeverywhere and remove old printer entry.

After these steps Octoeverywhere is working as expected and RatOS is clean.