Currently all the native applications are required to be at rootfs which could be upgraded with the system OTA, that is quite huge a bit than the third-party products.
Thus the new component to upgrade application requires the following to be done:
Progress to install the application: download, checksum and install.
Consider the case the application is working, when to install.
Define the package format.
Package registry must support the below features:
Get package by the following versions: Node.js, YodaOS and runtime API level.
Server pushing updates via MQTT/Wormhole.
Include the following files: JavaScript, JSON, libraries and executables.
[ ] app only need to provide API level to confirm whether it works properly, the version of the distribution channel is limited by the cloud
[ ] move third party app to /data, since every app directory should includes data directory and executable directory, only update the executable directory while update
[ ] support batch publish via MQTT
[ ] interaction while updating
- in this phase, we publish the app manually, automated publishing needs to be supported later
Currently all the native applications are required to be at rootfs which could be upgraded with the system OTA, that is quite huge a bit than the third-party products.
Thus the new component to upgrade application requires the following to be done:
Package registry must support the below features: