The new actions run still "build" the software into a zip package that can be uploaded to an OpenJBOD RP2040 board, however it will also build MicroPython with OpenJBOD built in via freezefs. This simplifies deploying and updating the firmware significantly.
Breaking down how this works:
The OpenJBOD software is cloned into the directory at build-time and forzen into a single python file using freezefs. The file will automatically extract itself to / on execution, unpacking all the necessary files.
The frozen package is imported by the _boot.py script that runs when MicroPython is first initialized. This means the files are overwritten on every boot. Note that config.json is excluded from this.
The new actions run still "build" the software into a zip package that can be uploaded to an OpenJBOD RP2040 board, however it will also build MicroPython with OpenJBOD built in via freezefs. This simplifies deploying and updating the firmware significantly.
Breaking down how this works:
The OpenJBOD software is cloned into the directory at build-time and forzen into a single python file using freezefs. The file will automatically extract itself to
/on execution, unpacking all the necessary files. The frozen package is imported by the _boot.py script that runs when MicroPython is first initialized. This means the files are overwritten on every boot. Note that config.json is excluded from this.