The config.json is in the /boot part of the image or the part that mounts when you are using an SD card and windows.
The config.json contains details like what application to join, the frist set of wifi creds, and other stuff.
If you have all the same type of devices, you should be able to provision a device with a master image of the right version for the device and swap in the right config.json for what application you want it to join.
Personally speaking, we use a sd card cloning service. The master I gave them was for a staging application where we name devices as we plug them in there and then move them to their final home. This flow could be improved but works for us.
I can’t give you details on how to pull config.json’s from the cli, but in the dashboard it is just another button.
But it looks like they have documentation on editing from the cli here.
Hi,
Actually, wifi configuration is no longer managed by the config.json file. Network connections are configured using NetworkManager configuration files. You can check this documentation https://www.balena.io/docs/reference/OS/network/2.x/
Such files can be edited in the downloaded image before you flash it.