Thanks @lifeeth for the update on AutoHat, its gonna be amazing when we have all our supported boards continuously testing themselves , its definitely gonna improve the support teams life a bunch by catching bugs and regressions .
For myself this week, I am mostly working on laying out some product features for 2017. In particular I am trying to scope out all the work done and still needed for the version 1 of our official multi-container feature. This feature is perhaps one of the most requested features we have ever had and I am really excited to get it built as soon as possible because it really allows for some cool usecases. Its also a really interesting feature to work on and spec out because it seeps into almost every part of our product from the Dashboard to the OS to the builders and API, so its really a full team effort. In its first form, the resin.io multicontainer feature should allow you to push a simple git repo with a
docker-compose.yml file at its root and it should all get seamlessly built and deployed across your entire fleet, working in symphony with all the usual features you already know and love in resin.io, like delta image pulls, webterminal, update strategies, etc.
Another feature I’m working on defining this week is the notion of “Organisations” or team accounts, which I know is a feature that has a massive impact on our customers and their development teams, so look forward to that landing in 2017 as well.
Besides the formal product spec’ing stuff, I’m also hoping to get some time to write a few bits of documentation on the resin.io container lifecycle and clear up some confusion in the docs on Environment variables and Configuration variables.
Thats pretty much all on my end for this week, so I nominate @Page because I’m curious on how the mysterious PineJS and API stuff if getting on?