|
| 1 | +/*! |
| 2 | +@page qtautoupdater_backends Backends overview |
| 3 | + |
| 4 | +@brief An overview of the avialable backends |
| 5 | + |
| 6 | +This page lists the different backends that are available, together with their features and how to use them. Refer |
| 7 | +to this page if you want to know details about a particular plugin. |
| 8 | + |
| 9 | +@tableofcontents |
| 10 | + |
| 11 | +@section qtautoupdater_backends_types Special Types |
| 12 | +This pages uses a few special types, which wrap different formats in which you can provide the arguments, mapped to |
| 13 | +a certain Qt type. Those are: |
| 14 | + |
| 15 | +- `list`: is processed by QtAutoUpdater::UpdaterBackend::readStringList. If a symbol is specified in parenthesis |
| 16 | +(e.g. `(;)`), that symbol is used as seperator instead of the default `,` |
| 17 | +- `pathList`: is processed by QtAutoUpdater::ProcessBackend::readPathList |
| 18 | +- `argList`: is processed by QtAutoUpdater::ProcessBackend::readArgumentList |
| 19 | + |
| 20 | +@section qtautoupdater_backends_qtifw Qt Installer Framework |
| 21 | +The QtIFW-Plugin allows you to use a maintenancetool of an |
| 22 | +[Qt Installer Framework](https://doc.qt.io/qtinstallerframework/index.html) installation to check for updates and to |
| 23 | +install them. It requires that an application was installed using a QtIFW installer that uses an online repository |
| 24 | +for the installation. The plugin focusses around the maintenancetool that is deployed with every QtIFW based |
| 25 | +installation. |
| 26 | + |
| 27 | +@subsection qtautoupdater_backends_qtifw_features Features |
| 28 | +- QtAutoUpdater::UpdaterBackend::Feature::CheckUpdates |
| 29 | +- QtAutoUpdater::UpdaterBackend::Feature::TriggerInstall |
| 30 | +- On linux and macOs: |
| 31 | + - QtAutoUpdater::UpdaterBackend::Feature::ParallelTrigger |
| 32 | + |
| 33 | +@subsection qtautoupdater_backends_qtifw_config Configuration |
| 34 | + Parameter | Type | Default Value | Description |
| 35 | +--------------------|-----------------------------------------------|---------------|------------- |
| 36 | + backend | QString | `"qtifw"` | The id of the backend. Must be that value |
| 37 | + path | QString | _special_ | The path to the maintenancetool that is used by the backend |
| 38 | + extraCheckArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to the maintenancetool when checking for updates |
| 39 | + silent | bool | `false` | Run the installer silently in the background |
| 40 | + extraInstallArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to the maintenancetool when installing updates |
| 41 | + runAsAdmin | bool | _special_ | Specifies, if the maintenancetool should be executed with elevated rights, when running it as installer |
| 42 | + |
| 43 | +The default value of the `path` depends on the platform beeing used. It is the path, where to expect the |
| 44 | +maintenancetool, assuming the current application is the primary binary that was installed using QtIFW. |
| 45 | + |
| 46 | +The default value of the `runAsAdmin` depends of the result of |
| 47 | +QtAutoUpdater::AdminAuthoriser::needsAdminPermission(path). The path here is the maintenancetool as specified in the |
| 48 | +settings. While this may work for most systems, it is recommended to always explicitly set this parameter to avoid |
| 49 | +problems. |
| 50 | + |
| 51 | +@section qtautoupdater_backends_pkgkit PackageKit |
| 52 | +The plugin based on [PackageKit](https://www.freedesktop.org/software/PackageKit/) is a general plugin that can work |
| 53 | +with any package managing system that supports PackageKit. This includes most popular linux distros like Arch, |
| 54 | +Debian or Fedora. Check the website to see if your distro supports PackageKit and how to configure it properly. |
| 55 | + |
| 56 | +On supported platforms, this plugin can be used to check for updates for certain packages and even install updates, |
| 57 | +if available. |
| 58 | + |
| 59 | +@subsection qtautoupdater_backends_pkgkit_features Features |
| 60 | +- QtAutoUpdater::UpdaterBackend::Feature::CheckUpdates |
| 61 | +- QtAutoUpdater::UpdaterBackend::Feature::CheckProgress |
| 62 | +- QtAutoUpdater::UpdaterBackend::Feature::PerformInstall |
| 63 | + |
| 64 | +@subsection qtautoupdater_backends_pkgkit_config Configuration |
| 65 | + Parameter | Type | Default Value | Description |
| 66 | +--------------------|-----------------------------------------------|-------------------|------------- |
| 67 | + backend | QString | `"packagekit"` | The id of the backend. Must be that value |
| 68 | + packages | @ref qtautoupdater_backends_types "list (;)" | _required_ | The list of packages that your application consists of |
| 69 | + |
| 70 | +To use the plugin correctly, you **must** specify the `packages` parameter. It should contain a _semicolon_ seperated |
| 71 | +list of all the packages that make your application (e.g. the primary package, extensions, language packages etc.). |
| 72 | +When checking for updates, only updates for the packages listed here are considered by the plugin. You must always |
| 73 | +enter the packages by the full name. Wildcards are not possible for now. |
| 74 | + |
| 75 | +@section qtautoupdater_backends_choco Chocolatey |
| 76 | +This plugin uses the [Chocolatey](https://chocolatey.org/) package manager for windows to check for updates and |
| 77 | +install them if requested. It is based around the `choco` executable and supports the |
| 78 | +[Chocolatey GUI](https://chocolatey.org/packages/ChocolateyGUI) as GUI to be shown to install updates. |
| 79 | + |
| 80 | +@subsection qtautoupdater_backends_choco_features Features |
| 81 | +- QtAutoUpdater::UpdaterBackend::Feature::CheckUpdates |
| 82 | +- If Chocolatey GUI is installed |
| 83 | + - QtAutoUpdater::UpdaterBackend::Feature::TriggerInstall |
| 84 | + |
| 85 | +@subsection qtautoupdater_backends_choco_config Configuration |
| 86 | + Parameter | Type | Default Value | Description |
| 87 | +--------------------|-----------------------------------------------|---------------------------------------------------------------|------------- |
| 88 | + backend | QString | `"chocolatey"` | The id of the backend. Must be that value |
| 89 | + packages | @ref qtautoupdater_backends_types "list" | _required_ | The list of packages that your application consists of |
| 90 | + path | @ref qtautoupdater_backends_types "pathList" | _system-path_ | A list of paths where to search for the `choco` executable. If not specified, the `PATH` environment variable is used |
| 91 | + extraCheckArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to choco when checking for updates |
| 92 | + guiExePath | QString | `"C:\Program Files (x86)\Chocolatey GUI\ChocolateyGui.exe"` | The path to the Chocolatey GUI binary |
| 93 | + extraGuiArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to Chocolatey GUI when installing updates |
| 94 | + runAsAdmin | bool | `true` | Specifies, if the Chocolatey GUI should be executed with elevated rights |
| 95 | + |
| 96 | +To use the plugin correctly, you **must** specify the `packages` parameter. It should contain a comma seperated |
| 97 | +list of all the packages that make your application, which is typically just a single package name. When checking |
| 98 | +for updates, only updates for the packages listed here are considered by the plugin. You must always enter the |
| 99 | +packages by the full name. Wildcards are not possible for now. |
| 100 | + |
| 101 | +@section qtautoupdater_backends_brew Homebrew |
| 102 | +The plugin uses the [Homebrew](https://brew.sh/) package manager for macOs to check for updates and install them. |
| 103 | +It can install updates in parallel, but also supports launching [Cakebrew](https://www.cakebrew.com/) as external |
| 104 | +install tool, if it is installed. |
| 105 | + |
| 106 | +@subsection qtautoupdater_backends_brew_features Features |
| 107 | +- QtAutoUpdater::UpdaterBackend::Feature::CheckUpdates |
| 108 | +- QtAutoUpdater::UpdaterBackend::Feature::PerformInstall |
| 109 | +- If Cakebrew is installed: |
| 110 | + - QtAutoUpdater::UpdaterBackend::Feature::TriggerInstall |
| 111 | + - QtAutoUpdater::UpdaterBackend::Feature::ParallelTrigger |
| 112 | + |
| 113 | +@subsection qtautoupdater_backends_brew_config Configuration |
| 114 | + Parameter | Type | Default Value | Description |
| 115 | +--------------------|-----------------------------------------------|---------------|------------- |
| 116 | + backend | QString | `"homebrew"` | The id of the backend. Must be that value |
| 117 | + packages | @ref qtautoupdater_backends_types "list" | _required_ | The list of packages that your application consists of |
| 118 | + cask | bool | `false` | The package is a cask instead of a normal homebrew package |
| 119 | + path | @ref qtautoupdater_backends_types "pathList" | _system-path_ | A list of paths where to search for the `brew` executable. If not specified, the `PATH` environment variable is used |
| 120 | + extraUpdateArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to `brew update` when checking for updates |
| 121 | + extraOutdatedArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to `brew outdated` when checking for updates |
| 122 | + extraInstallArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to `brew install` when installing updates |
| 123 | + cakebrewPath | @ref qtautoupdater_backends_types "pathList" | _system-apps_ | A list of paths where to search for the `Cakebrew` app bundle. If not specified, the systems standard app locations (QStandardPaths::ApplicationsLocation) are searched |
| 124 | + extraCakebrewArgs | @ref qtautoupdater_backends_types "argList" | _empty_ | Additional arguments to be passed to Cakebrew when installing updates |
| 125 | + |
| 126 | +To use the plugin correctly, you **must** specify the `packages` parameter. It should contain a comma seperated |
| 127 | +list of all the packages that make your application, which is typically just a single package name. When checking |
| 128 | +for updates, only updates for the packages listed here are considered by the plugin. You must always enter the |
| 129 | +packages by the full name. Wildcards are not possible for now. If your package is a cask, set the variable. |
| 130 | + |
| 131 | +@section qtautoupdater_backends_play Google Playstore |
| 132 | +When deploying your app via the [Google Playstore](https://play.google.com/store) for Android, you can use this |
| 133 | +plugin to check for updates and even install them. This works fine for most phones, but be aware that some might |
| 134 | +have disabled various APIs required for this plugin to work. |
| 135 | + |
| 136 | +@subsection qtautoupdater_backends_play_features Features |
| 137 | +- QtAutoUpdater::UpdaterBackend::Feature::CheckUpdates |
| 138 | +- QtAutoUpdater::UpdaterBackend::Feature::PerformInstall |
| 139 | +- QtAutoUpdater::UpdaterBackend::Feature::TriggerInstall |
| 140 | +- QtAutoUpdater::UpdaterBackend::Feature::ParallelTrigger |
| 141 | + |
| 142 | +@subsection qtautoupdater_backends_play_config Configuration |
| 143 | + Parameter | Type | Default Value | Description |
| 144 | +--------------------|-----------|---------------|------------- |
| 145 | + backend | QString | `"playstore"` | The id of the backend. Must be that value |
| 146 | + debug | bool | `false` | If set to true, the [FakeAppUpdateManager](https://developer.android.com/reference/com/google/android/play/core/appupdate/testing/FakeAppUpdateManager.html) is used to simulate an update installation |
| 147 | + autoResumeInstall | bool | _special_ | If enabled, the plugin will check if installations need to be continued on it's initialization and do so, if required. |
| 148 | + |
| 149 | +The `autoResumeInstall` will be set to true by default if initialized from an activity. When run from the |
| 150 | +background, it is false instead. |
| 151 | + |
| 152 | +@section qtautoupdater_backends_webquery Custom WebQuery backend |
| 153 | +This backend can be used if none of the other backends fit your distribution method. While it is recommended to |
| 154 | +create a custom plugin for such cases, for many variants this plugin suffices. It can query a webserver for |
| 155 | +JSON-encoded information about available updates, download a binary or update package of any kind and execute a |
| 156 | +selected binary to perform the update installation. |
| 157 | +*/ |
0 commit comments