Releases: OctoFarm/OctoFarm-Companion
Release Candidate 1 for OctoFarm-Companion 0.1
THIS IS A CANDIDATE AND NOT READY FOR PRODUCTION USE
Changes:
- Added 90% test coverage
- Reworked some repeated code
This release marks the beginning of the OctoFarm-Companion plugin, which will functions as a glue layer between OctoPrint and OctoFarm. For now the plugin will make printer registration a breeze, as we remove the need for mDNS or SSDP using the Autodiscovery Plugin and announce the OctoPrint instance to OctoFarm. In future releases there is a lot more we will add.
Notes before using:
- OctoFarm needs OctoFarm/OctoFarm#550 to be checked out or merged in order for the plugin to find its buddy plugin called
OctoPrint Companion
on the OctoFarm side. WHAT OCTOFARM PLUGINS??? YES YOU READ IT CORRECTLY 🥳 - Currently there is nothing to convert the announced OctoPrint device on OctoFarm's side to an actual printer. We simply lack the User Interface right now. This is a core feature to be finished soon.
- OctoPrint instances behind a proxy, in docker, VM, Unraid, VPN etc will have issues to post the right IP address and or port. This is not easily fixed, but we will work on making this a breeze as well!
We have 2 options for fixing the proxy issue: option 1 - manual announcing via the OctoPrint website as this website will know how to access the OctoPrint device as the site itself is already resolved. Option 2 - automatic setup of what is called a http tunnel or bridge. We have experimented with the http bridge and this seems to be a very viable option. It will however take some time before this is released as it has a huge impact on OctoFarm's implementation.
Please read the README to use this plugin
https://github.com/OctoFarm/OctoFarm-Companion
Please read the changelog to see the intricate features.
https://github.com/OctoFarm/OctoFarm-Companion/blob/main/CHANGELOG.md
Release Candidate 1 build 2 for OctoFarm-Companion 0.1
THIS IS A CANDIDATE AND NOT READY FOR PRODUCTION USE
This prerelease marks the beginning of the OctoFarm-Companion plugin, which will functions as a glue layer between OctoPrint and OctoFarm. For now the plugin will make printer registration a breeze, as we remove the need for mDNS or SSDP using the Autodiscovery Plugin and announce the OctoPrint instance to OctoFarm. In future releases there is a lot more we will add.
Notes before using:
- OctoFarm needs OctoFarm/OctoFarm#550 to be checked out or merged in order for the plugin to find its buddy plugin called
OctoPrint Companion
on the OctoFarm side. WHAT OCTOFARM PLUGINS??? YES YOU READ IT CORRECTLY 🥳 - Currently there is nothing to convert the announced OctoPrint device on OctoFarm's side to an actual printer. We simply lack the User Interface right now. This is a core feature to be finished soon.
- OctoPrint instances behind a proxy, in docker, VM, Unraid, VPN etc will have issues to post the right IP address and or port. This is not easily fixed, but we will work on making this a breeze as well!
We have 2 options for fixing the proxy issue: option 1 - manual announcing via the OctoPrint website as this website will know how to access the OctoPrint device as the site itself is already resolved. Option 2 - automatic setup of what is called a http tunnel or bridge. We have experimented with the http bridge and this seems to be a very viable option. It will however take some time before this is released as it has a huge impact on OctoFarm's implementation.
Please read the README to use this plugin
https://github.com/OctoFarm/OctoFarm-Companion
Please read the changelog to see the intricate features.
https://github.com/OctoFarm/OctoFarm-Companion/blob/main/CHANGELOG.md