Additional octoprint instance

[louispires]

No description provided.

[AmedeeBulle]

While this might work for you, this is not ready for general use...

• Second instance isn't optional
• It doesn't integrate with the haproxy and webcam daemon

(io.resin.features.dbus: '2'doesn't make sense BTW -- it is. boolean flag...)

While it require some more development / testing, the cleaner way of running multiple instances would be to run multiple instances of the complete stack and use --project-name to isolate the networks of the different stacks.
Additionally we need to:

• use --env-file option to select an alternate configuration file
• Add configuration options to
  • listen on different ports on the host
  • Use a different volume to store the data

I'll try to get this done one of these days...

[louispires]

yeah all good man.

I was just playing around and got it working pretty well.

Reverted to a stock RPI Lite Image, installed docker and then just installed two Images on separate ports.

Also only linked the camera up to one of the containers.

One problem I ran into which you might be able to resolve, when I restart the Printer/RPi the USB devices sometimes swap around. As I have 2 instances now and they are named according to the printer that they are running, it does cause some confusion at times.

[AmedeeBulle]

I have pushed some changes through #11 which allows you to run 2 independent stacks.

Having the right printer on the right instance is a challenge as you can't predict which one will come first.
What you could do is writing udev rules so that the printers consistently get the same device name (this article might help you) -- assuming your printers have a different USB signature...