Note that assets don't require you to recompile the firmware. Adding an asset consists of adding new data to the firmware envelope without changing the elf file that is in the envelope. @kasperl, do we expose the asset functionality nicely in Jaguar?

That said, there is probably an easier way. You could just store the configuration in flash (see https://libs.toit.io/device/class-FlashStore).
You could either jag run a program that saves the corresponding information in the flash, or do it like Jaguar: start a small http server that accepts the configuration and writes it to flash.

I could imagine the following work-flow:

• flash Jaguar
• modify a config.toit file
• jag run config.toit which then writes the configuration to flash.

Alternatively; more sophisticated:

• flash Jaguar
• jag run config_updater.toit which launches an http server
• push the configuration with curl, a separate tool, or using a web-browser (assuming config_updater serves a nice html page).

Turned out to be pretty straightforward. No idea how I did not notice the --assets option for container and run before.

build/host/sdk/tools/assets -e device-1.assets create
build/host/sdk/tools/assets -e device-1.assets add config device-1.json
jag flash --name device-1
jag container install --device device-1 --assets=device-1.assets light-monitor sensor-monitor.toit

rinse, repeat for device 2, 3, 4 etc. I generate the json files from a script locally.

Super-easy. Thank you! I think toit already saved me more time fuzzing around with SDKs, cross compilers and all that pain than I put into the first version of these little critters.