Hi @brice, one more thing, you can create
Dockerfile variants that can be specific to specific devices types and can exists next to each other in your code. This is using the device type 's slug, or the architecture, and priorities are observed by the builder in order of specificness.
For example, if you want one for the NUC, you could have
Dockerfile.intel-nuc (most specific, extension same as
%%RESIN-MACHINE-NAME%% would be in a template)
Dockerfile.amd64 (architecture level, extension same as
%%RESIN-ARCH%% would be in your template)
Dockerfile.template (least specific, captures all device types, and can use e.g. those above template variables)
So in your case you could have
.raspberrypi3 depending on which Pi you mean), and
Dockerfile.jetson-tx2, next to each other, and you could push the same repo to the 3 different applications (maintaining the three different git remotes).
Our documentation is a bit sparse on this, but we are trying to gather things in a non-confusing way. An example of this being used (on the architecture level) you can see in our Multicontainer Getting Started project, the haproxy service: https://github.com/resin-io-projects/multicontainer-getting-started/tree/master/haproxy
Let us know how does it work if you try it out!