We have been progressing on the architecture for how to best do CI and CD.
At the moment we have a basic setup to build and then use ansible and terraform.
thats a basis for servers and clouds where we are nice and agnostic to a degree.
Now we should consider to do the same for embedded. Why ?
small cheap computers are awesome for running this type
The whole point is data privacy.
we have no non golang dependencies so its easy for us. We designed for this.
We will later add a dynamic DNS / Reverse PRoxy to allow these devices to be "public". We know how to do that.
We have been progressing on the architecture for how to best do CI and CD.
At the moment we have a basic setup to build and then use ansible and terraform. thats a basis for servers and clouds where we are nice and agnostic to a degree.
Now we should consider to do the same for embedded. Why ?
SO here is what i am thinking:
Flash Rasp PI and other boards properly with this https://github.com/periph/bootstrap/issues/10
, and then it will be part of CI https://github.com/periph/gohci/tree/master/cmd/gohci-worker
This is clean and sort of matches the pattern / architype of how we are doing CI / CD with Ansible, Terraform and Caddy flow..
This is NOT urgent, but i want to start this discussion ...