Wednesday, January 15, 2025
3 changes · saas-18.1
Enhancements to existing features
This update adds simple developer commands to temporarily disable selected IoT box features or device actions during development. It helps teams test and iterate faster without changing source code, with no direct impact on normal business users.
Original PR description
While developing, we often disable features like the db checkout and the IoT handlers download to save some time. Now, instead of going in the code and comment the lines we want to remove, we can just type: - `devtools disable general`: to disable general features (checkout, handlers download), - `devtools disable actions <optional action name>`: to disable a device action (printing for example). **Note:** by default, if you don't specify `<action name>`, it will disable all actions. Task: 4291487
The IoT box image version is now generated automatically from the build date instead of being updated by hand for each release. This reduces manual release work and lowers the chance of publishing an image with an outdated or incorrect version number.
Original PR description
Before this PR, the IoT box version (e.g 25.01 for an image built in January 2025) was changed manually whenever a new image was released. After this PR, the version string is generated automatically based on the date at build time. Also, an unused `VERSION` variable was removed from the build script. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The IoT box setup now makes common text editors keep files under the expected Odoo ownership. This reduces the risk of configuration or maintenance issues caused by files accidentally changing ownership during edits.
Original PR description
In order to ensure file ownership does not change, we updated `nano` and `vim` aliases to force perform as `odoo` user.