Major update of DriversCloud application and infrastructure

Written by charon

Publication date: {{ dayjs(1773220521*1000).local().format("L").toString()}}

This article is an automatic translation

A new series of enhancements has just been rolled out, both to the monitoring application and to the site and server infrastructure. This update enhances the reliability, data consistency and overall stability of the service.

🔧 Monitoring application: new architecture and improved hardware management

Complete overhaul of internal architecture to handle persistent sensors and hardware changes more robustly.
Fixed a problem where the sensor list did not display some duplicate hardware.
The machine identification system has evolved:

The application is no longer based on network name.
A unique identifier for a given account generated at installation is now used.
This identifier only changes if the motherboard or CPU model differs on the same account.

🌐 Website: new database structure

The database has been restructured to enable different departments in the same configuration to share their data.
Migration processing takes 2 to 3 hours (sometimes a little longer).

During this period, it is normal that your configurations temporarily do not appear in your account.

🔐 Accounts and authentication: simplified and more reliable

All applications now require an account (classic or disposable).
- The old anonymous detections have been removed from the code.
- For offline configurations, a disposable account can be created in a matter of seconds.
Bugs fixed when refreshing authentication tokens:

Some users could be disconnected, notably at machine startup.
System services now wait until the network stack is fully loaded.
The token is now automatically refreshed 5 minutes before expiration, in addition to handling authentication failures.

🖥️ DriversCloud application: migration to Tauri v2