{"id":4315,"date":"2022-09-05T11:09:01","date_gmt":"2022-09-05T11:09:01","guid":{"rendered":"https:\/\/www.petecodes.co.uk\/?p=4315"},"modified":"2022-09-15T14:33:56","modified_gmt":"2022-09-15T14:33:56","slug":"octoprint-for-the-seeed-studio-reterminal-live-blog-day-1","status":"publish","type":"post","link":"https:\/\/www.petecodes.co.uk\/octoprint-for-the-seeed-studio-reterminal-live-blog-day-1\/","title":{"rendered":"OctoPrint for the Seeed Studio reTerminal – Live Blog – Day 1"},"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 going through my initial plans, cloning repos, Looking at Plugins and getting the VS Code OctoPrint Development Environment Setup.<\/p>\n\n\n\n
The first thing I expected I’d need to do was to fork the GitHub Repos for OctoPrint <\/a>and OctoPi<\/a>, which I’ve done here;<\/p>\n\n\n\n OctoPrint:<\/strong> https:\/\/github.com\/pjgpetecodes\/OctoPrint-reTerminal<\/a><\/p>\n\n\n\n OctoPi:<\/strong> https:\/\/github.com\/pjgpetecodes\/OctoPi-reTerminal<\/a><\/p>\n\n\n\n Next up, it’s time to start searching for docs for how to get started developing OctoPrint… <\/p>\n\n\n\n Nicely, the docs for OctoPrint are fantastic, and I quickly find a section on how to get started with the Development<\/a>, which details how to get everything including the IDE setup.<\/p>\n\n\n\n Happily, there’s even a guide for setting up my favourite editor, VS Cod<\/a>e!<\/p>\n\n\n\n