We’ve got a strange use case.
We’d like to deliver a preloaded multi-container image with an app in one container and NodeRED in the second container.
The device should not connect to balena on the first boot. Our app connects to our server where the user can enable connecting to balena.
That way, if they choose not manage the device with balena (which costs money), they can still use NodeRED to “do stuff”.
Is there a way to prevent the supervisor from connecting at startup?
Can Supervisor API be used to start the connection?