Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-open:practical:software:admins [2024/01/27 21:18] – [Admin] pczekalski | en:iot-open:practical:software:admins [2025/03/11 11:24] (current) – [Admins's Guide] pczekalski | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Admins' | ====== Admins' | ||
| - | <todo @pczekalski> | + | The system has two kinds of administrators: |
| - | The system has two kinds of administrators: | + | To understand activities and relations, it is essential to recognise system-building components (figure {ref> |
| + | <figure vrelsoftware2> | ||
| + | {{ : | ||
| + | < | ||
| + | </ | ||
| ===== Super Admin ===== | ===== Super Admin ===== | ||
| Line 13: | Line 17: | ||
| * User management: | * User management: | ||
| * editing User's data, | * editing User's data, | ||
| - | * deleting | + | * delete the User's project files (Cleanup). |
| * Managing group of users: | * Managing group of users: | ||
| * creating and deleting user groups, | * creating and deleting user groups, | ||
| Line 26: | Line 30: | ||
| * cleaning up devices (deletes compilation targets), | * cleaning up devices (deletes compilation targets), | ||
| * Managing User's bookings (per device). | * Managing User's bookings (per device). | ||
| + | |||
| + | Below there are some hints and important information: | ||
| + | - User Groups bind Users and Devices: Users can book Devices if both are in the same group. The User can be a member of many groups. Groups typically reflect student groups (such as the Dean's group or laboratory team), and devices assigned to the group reflect module-related resources that are needed to perform lab work. | ||
| + | - Admin-level access to the Bookings is possible via the Devices menu (then expand the group and the device and check for Bookings in the context menu). | ||
| + | - Users' projects (source codes) can be cleaned up in the Users menu. | ||
| + | - Laboratory compiled and temporary files can be cleaned up in the Devices' | ||
| + | - Compiler service uses a single source file on the input, which is PlatformIO-based. Thus, all source codes constituting a project are single cpp (or other) files + platformio.ini files. | ||
| + | |||
| + | ==== Admin: device configuration ==== | ||
| + | Device configuration is the most complex part of the administration process. It requires the correct configuration of the end node proxy service regarding the specification of the target IoT device it manages. It is a compilation service (figure {{ref> | ||
| + | The device configuration supports several configuration parameters, many of which may be redundant or unnecessary, | ||
| + | Commands to compile and upload firmware (or configuration) are Admin-defined. Besides common configuration parts such as name, location, and description, | ||
| + | * Device reset (reboot, restart) | ||
| + | * Commands copying from the frontend/ | ||
| + | * copies '' | ||
| + | * copies '' | ||
| + | * Code compilation, | ||
| + | * remember to remove previous compilation results before subsequent compilation so that if compilation fails, the existing compiled code won't be mistaken for the new one. | ||
| + | * Verification of the successful compilation - enables Upload button - the command should check if compilation was successful and return 1 otherwise 0. | ||
| + | * Code execution (i.e. firmware upload) | ||
| + | <note tip> The Aforementioned actions can have more than one command, and each command can be an SSH or CMD (bash) command.</ | ||
| + | <note tip> | ||
| + | |||
| + | |||
