Recommended client configurations
Before you start developing or deploying to production, you should check that your configuration file has appropriate settings for your use case.
The configuration file and exact parameters depend on how you use OTA Connect:
-
If you’re building disk images that contain aktualizr or libaktualizr, you need to update your build configuration.
-
If you’re using a standalone version of aktualizr that you’ve installed locally, you need to update the client configuration.
If you are building a disk image that contains aktualizr, your configuration will be the local.conf file.
-
You’ll find this file in the
conf
subdirectory of the of your build project.
For more information, see the build configuration reference and the sample build procedures
Configuration | Description |
---|---|
|
Interval between polls (in seconds). The default polling internal designed to make it convenient for you test and develop OTA update functions. |
|
Forces installation completion. Causes a system reboot in case of an ostree package manager. Emulates a reboot in case of a fake package manager. You’ll want to enable this option when developing because it’s more convenient. |
|
To troubleshoot problems that you might encounter during development, we recommend that you enable persistent |
|
We also recommending running with debug logging enabled in aktualizr during development. |
Configuration | Description |
---|---|
|
When moving to production you’ll want to have a much longer interval. In fact, for production, we don’t support intervals less the 1 hour (3,600 seconds). Longer internals help you to reduce the internet bandwidth and power consumption for your devices. We recommend an internal between 1 and 7 days (86,400 to 604,800 seconds) |
Remove |
If you followed our recommendation to enable automatic rebooting for development, you should disable again for production. |
Remove |
If you followed our recommendation to enable log persistence for development, you may want to disable it for production to save space on your device. |
Remove |
If you followed our recommendation to enable debug-level logging for development, you may want to disable it for production to reduce file writes. |
If you are running standalone aktualizr, your configuration file will be a .toml file.
You configure aktualizr by creating and updating a *.toml
file in one of the following directories:
-
/usr/lib/sota/conf.d
-
/etc/sota/conf.d/
For more information and links to sample configuration files, see the client configuration reference.
Configuration | Description |
---|---|
|
Interval between polls (in seconds). The default polling internal designed to make it convenient for you test and develop OTA update functions. |
|
Forces installation completion. Causes a system reboot in case of an ostree package manager. Emulates a reboot in case of a fake package manager. You’ll want to enable this option when developing because it’s more convenient. |
Configuration | Description |
---|---|
|
When moving to production you’ll want to have a much longer interval. In fact, for production, we don’t support intervals less the 1 hour (3,600 seconds). Longer internals help you to reduce the internet bandwidth and power consumption for your devices. We recommend an internal between 1 and 7 days (86,400 to 604,800 seconds) |
|
If you followed our recommendation to enable automatic rebooting for development, you should disable again for production. |