I looked there but they set up OctoPrint differently on the Pi. I have a PC.
In what ways? Pi is still on Linux. The concepts will be fairly similar, and the effort will be similar.
Raspbian is basically Debian and Debian is basically just Linux.
Well, most guides start with the custom image for the Rpi. I can't find some of the files they want me to copy and mod, so I get stuck. For instance, in the guide linked in the megathread, it says to run " sudo cp /etc/default/octoprint /etc/default/octoprint2". My environment doesn't have an /etc/default/octoprint.
Searching Guy's octopi repository for /etc/default/octoprint
turns up the file you appear to be looking for.
OctoPi/src/modules/octopi/filesystem/root/etc/default/octoprint
So it looks like the OctoPi image includes this set of /etc files which help to make the magic happen.
You'll have to forgive me, I'm pretty new to Linux and all that went right over my head.
My /ect/default/ doesn't have an "octoprint" directory or file. Do I need to put something here?
We're at the point now where you should begin to appreciate the value that Guy's done by packaging OctoPrint and then making a variety of automated adjustments to Raspbian so that it works rather smoothly out of the box.
You can see that he's made adjustments in the form of a service which autostarts OctoPrint, the mjpg_streamer as well as creating the necessary /etc/sudoers.d/
โrelated files to allow the pi
user to do a couple of things without providing the password for sudo.
Personally, I don't really think that running multiple printers on a single computer is a good idea. If you believe that you have the extra power on your box to do that, then it's your setup. But now you're asking someone like myself to take that journey with you and to talk you through it. From the 80/20 rule, I like to setup things for 80% of the people. The outliers probably need to know what they're doing in a case like this.
If I generally point you in the direction where you could get the answers to your questions and you lack the experience at the moment for success, then it's up to you to decide if you want to challenge yourself, "go to school" on the code itself and learn how to do this... or to simply choose an easier path for yourself. You've just said "I'm pretty new to Linux" and you want to do something rather advanced in Linux by setting up haproxy
soon for four instances. I'd like to say that I have the quality time to take you through this step by step but I've got other things I should be doing.
Read things. Learn. Challenge yourself. Make this a great setup if you want to but it's going to cost you more time at this. Good luck.
If you are this new to Linux, doing the config work necessary for multiple installs is gonna be difficult. I'm gonna merge this to the multiple multithread.
Okay, yes, I'm new to linux, but I'm willing to learn. I'm just not sure where to start. I understand that you "don't support it" but I know it can be done. Can someone answer my question?
How do I point OctoPrint to a different config.yaml?
Now that you're in the megathread for this topic, back-read it and see how it's done.
Is there plans to have like an OctoServer setup so one can go to Site, and see cameras for all Registered Octoprint devices? (so yuou can see the print happening, cancel failed print, even start a print from remote, see temps of everything
One Dashboard shows status of your printers./ Kinda like Repetier Server
now I am not talking running all printeres off 1 Pi, I want to see a frint end that see;s all tghe Pis into 1 Dashboard
maybe this has bneen discussed before
Search the forum here for the word "multiple" and you can read that people have created solutions and are working on new ones for dashboards like you're describing.
Didn't read the entire thread, but this simple bash script I put together may be useful for some folks: https://github.com/paukstelis/octoprint_deploy
Looks good
Thank you
does it work with printers with no serial ?
I assume you mean no serial number? It will work for printers with no serial number, but the serial auto-detect will obviously fail. In those cases you have to go in and edit the udev rules to include some identifying characteristics.
There's a difference between a firmware's serial number and the printer board's serial number as presented to the udev
process.
If you're trying to connect to multiple same-manufacturer/same-model boards and they don't present a serial number to lsusb
or dmesg
then look at another method of doing so.
Hey all. just a question for the megathread readers here... Would the RPI 4 be powerful enough to manage 2 printers?
Certainly.
As a RasPi 3B+ can do, a 4B can do to.
But keep in mind, that when you got problems with the dual server, two prints can be spoiled.