{"id":4324,"date":"2022-09-08T13:24:28","date_gmt":"2022-09-08T13:24:28","guid":{"rendered":"https:\/\/www.petecodes.co.uk\/?p=4324"},"modified":"2022-09-15T14:37:48","modified_gmt":"2022-09-15T14:37:48","slug":"octoprint-for-the-seeed-studio-reterminal-live-blog-day-4","status":"publish","type":"post","link":"https:\/\/www.petecodes.co.uk\/octoprint-for-the-seeed-studio-reterminal-live-blog-day-4\/","title":{"rendered":"OctoPrint for the Seeed Studio reTerminal – Live Blog – Day 4"},"content":{"rendered":"\n
This post is a series of posts in which I detail my journey to bring OctoPrint to the Seeed Studio reTerminal.<\/p>\n\n\n\n
In today’s post we’ll be with learning how to make an OctoPrint Plugin including how to make it distributable.<\/p>\n\n\n\n
I’d left the development environment running last night, and when I returned to VS Code today, there’s a whole heap of yellow debug messages;<\/p>\n\n\n