Oh, cool, just checking your site as well, it's a very real issue you solve, have some spare Raspberry Pi to try it out.
It feels like a big change in dev thinking that I cannot ssh into the board anymore, but also very interesting.
By the way, I see that you'll be supporting the SabreLite soon. Would it mean to be able to support other i.MX6-based boards like the VIA VAB-820 [1] or the UDOO?
the idea is to make deployments repeatable, so while we may allow sshing in the future, it will be for diagnostic/experimentation reasons, not for altering the device state, so I think you understand the problem we're solving pretty well.
We keep adding devices and will soon release a guide on how users can add their own devices to the mix. That said, the primary determinant on whether we can support a device is whether a yocto/openembedded BSP exists and is relatively modern (uses a kernel above 3.8). If that exists, it's almost certain that resin support will be relatively easy. Happy to chat more, email in profile.
Yeah, i wasn't really missing SSH, as "I never thought to take away SSH" and actually it makes sense to have a different deployment and management mode. :)
And yeah, as a lucky chance, VAB-820 just had a yocto layer released with 3.10.17 [1]. Looking forward to see where this is headed!
It feels like a big change in dev thinking that I cannot ssh into the board anymore, but also very interesting.
By the way, I see that you'll be supporting the SabreLite soon. Would it mean to be able to support other i.MX6-based boards like the VIA VAB-820 [1] or the UDOO?
[1]: http://www.viaembedded.com/en/boards/pico-itx/vab-820/