Dell ThinOS 10.x App Builder User Guide

Create CI application packages

Build CI application packages by adding app details, resolving dependencies, setting permissions, previewing builds, and signing for deployment.

1. Open App Builder from the ThinOS taskbar of the endpoint device.
2. In Files & details tab:
   1. Go to Application Deployment Mode, and select Isolated mode.
   2. Enter the required inputs:
      • Application Name: Enter the application name.
        NOTE:Do not rename the application name. If you rename it, ensure that you close App Builder and repeat the process again.
      • Version: Enter the version.
      • Debian Packages: Upload the supported .deb files that are downloaded from trusted sources using USB device.
      • Executable Path: Enter the binary path to launch the app (For example: /usr/bin/<appname>). This field is autopopulated if the binary is detected, but you can also manually specify a custom path if needed.
      • App Icon: Upload the required icon for the application. Supported file types: .png, .jpg, .jpeg, and .ico.

      NOTE:To find the executable binary path from a .deb file, run dpkg -c <appname>.deb and to list only file paths, run dpkg -c <appname>.deb | awk '{print $6}'. You can use the output paths /usr/bin/appname to identify the executable binary path for launching the application. Alternatively, unpack the .deb file and check the .desktop file to locate the binary path.
3. Click Next.
4. In the Dependencies tab, verify the details.
   NOTE:A listed missing dependency may not indicate that the file is absent, it can result from a name or version mismatch with the expected dependency.

   NOTE:Dependencies are categorized as Available (already on the ThinOS client), Downloadable (from Ubuntu repositories), and Missing (Custom) (must be manually uploaded by returning to Step 1).

   NOTE:You can view the dependency report and download the log and report using the Save Report button.
5. Click Next.
6. In Permissions tab, upload a configuration file type .txt, .ini, .config,.properties, .cfg, or .conf, and set application-level permissions.
   Modify the permission as per your requirement.

   • USB Access: Enable/Disable
   • Webcam: Enable/Disable
   • Network: Configuration
   • Microphone: Enable/Disable
   • Printing: Enable/Disable
   • Bluetooth: Enable/Disable
   • Persistent Storage

   NOTE:In Isolated Mode, peripherals must be manually enabled or disabled, whereas in Native Mode, they are automatically allowed to access it.
7. Click Next.
8. In Preview tab, you can verify the build process and validate the application.
9. Launch the application and verify it by validating peripheral access configurations.
   Once the build process begins, the admin or user can monitor the logs, and a report is generated automatically upon completion.

   NOTE: In Isolated Mode, if you encounter issues with peripherals during application preview (such as webcam or audio access), return to Step 3 and enable the required access by selecting the appropriate checkboxes.
10. Click Exit Preview, and then click Next.
11. In Bundle tab, click Browse File(s) to add the signed certificate. Supported file type: .pem.
    NOTE:You can upload an existing certificate if you have already generated one.
12. Click Bundle & Sign.
    Once Bundle and Sign is complete, you can save the created application package and either upload it using WMS or APT, or copy it to a USB.
13. Click Save Application.
    The application is saved successfully and moved to USB successfully. To upload the application package to WMS or APT, see Upload package using WMS or APT.

    NOTE:Save the application before closing the App Builder to prevent loss of any unsaved changes.

    For more information about enabling Auto-launch CI application and Show Apps Before Login, see Auto‑Launch CI applications and Application visibility before login in to the VDI Menu.