@techielew I was just reading the scroll back, this is quite interesting, it also sounds almost iden
@techielew I was just reading the scroll back, this is quite interesting, it also sounds almost identical to a hardware in the loop ci setup with the key differences being we push from users instead of source control (I guess it would be encumbering for users to push git to flash the hardware?) And that users want to poke/shoogle/look at the hardware instead of automated tests.
I'd be interested to discuss further / help with this.
My gut feeling re the aws thing is I'm on the side of the $5 linode - I'm generally of the opinion that if the part talking to hardware needs to scale for users the architecture was built wrong - we usually run these things on something in the raspberry pi territory
P.s. - if you do use a PI, you get the gpios/busses so it's easy to hang off a couple of i2c/spi devices to stimulate various parts of the system, the linode would basically serve some rpc interface which should be very light and the "fancy web stuff" can be done client side - the linode is more there so that you arent exposing a pi in your house to the nasty world
I'd be interested to discuss further / help with this.
My gut feeling re the aws thing is I'm on the side of the $5 linode - I'm generally of the opinion that if the part talking to hardware needs to scale for users the architecture was built wrong - we usually run these things on something in the raspberry pi territory
P.s. - if you do use a PI, you get the gpios/busses so it's easy to hang off a couple of i2c/spi devices to stimulate various parts of the system, the linode would basically serve some rpc interface which should be very light and the "fancy web stuff" can be done client side - the linode is more there so that you arent exposing a pi in your house to the nasty world
