Skip to content

Commit

Permalink
Merge remote-tracking branch 'origin/main'
Browse files Browse the repository at this point in the history
  • Loading branch information
agnetemoos committed Jan 17, 2025
2 parents bfe414e + b75c598 commit ca5bb7c
Show file tree
Hide file tree
Showing 4 changed files with 30 additions and 3 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
27 changes: 27 additions & 0 deletions docs/brugervejledninger/os2borgerpc-client-opdateringer/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title: OS2BorgerPC-Client opdateringer
nav_exclude: false
parent: Brugervejledninger
---

OS2BorgerPC og OS2BorgerPC Kiosk installationer kommunikerer med administrationssiden via en klient kaldet <a href="https://github.com/os2borgerpc/os2borgerpc-client" target="_blank" rel="noopener">OS2BorgerPC-client.</a>

Som standard er OS2BorgerPC og OS2BorgerPC Kiosk installationer sat op til automatisk at tjekke for opdateringer af klienten og installere nyere versioner, hvis de findes.

Den aktuelt installerede version af OS2BorgerPC-client på en enhed kan findes under nøglen **_os2borgerpc.client_version**.
![Installeret version af os2borgerpc-client](/assets/images/brugervejledninger/os2borgerpc-client_installed.png)

## Manuel styring af version
Det er muligt at styre, hvilken version af OS2BorgerPC-client der bruges på en enhed, ved at konfigurere nøglen **os2borgerpc_client_version**.

Denne indstilling kan angives på følgende niveauer:

1. Computer-specifik konfiguration
2. Gruppe-konfiguration
3. Site-konfiguration

Konfigurationerne prioriteres i nævnte rækkefølge.

![Ønsket version af os2borgerpc-client](/assets/images/brugervejledninger/os2borgerpc-client_desired.png)

Hvis denne konfiguration ikke er angivet, vil systemet automatisk tjekke for opdateringer som beskrevet ovenfor.
6 changes: 3 additions & 3 deletions docs/teknisk dokumentation/script_metadata.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,6 @@ Script metadata variables
| `parameters` | The list of parameters that the script expects to receive. <br> Each parameter is described by an array of 4 key/value pairs. <br> - `name`: The name of the parameter<br> - `type`: Supported values are `boolean`, `string`, `int`, `text_field`, `file`, `password`<br> - `default`: Default value of the parameter. `null` if none.<br> - `mandatory`: Required parameter? `true` or `false` <br> If the script expects leave the parameters-variable empty. | Required |
| `compatibility` | Info about image and version compatibility. Supported values are: `20.04`, `22.04`, `24.04`, `BorgerPC` and `Kiosk`. More than one value can be supplied.| Optional |
|`in_image`| Sometimes scripts get absorbed by the images, meaning that the script functionality is built into the image (borgerpc/kiosk) thereby making the script obsolete. When this happens please provide the image name and version tag here.| Optional |
| `metadata` | Information that is used to control how the script is referenced and displayed in the admin-site. <br> Supported optional properties are: <br> `hidden`: Should the script be visible in admin-site UI? `true` or `false`. Defaults to `false` <br> `security`: Should the script be shown in 'Sikkerhedsscripts' in admin-site UI? `true` or `false`. Defaults to `false` <br> `uid`: Special scripts that the admin-site needs to reference. The uid *must* be unique, which also implies that only one version can be present in admin-site at any given time. `string`. Defaults to `null` | Optional |


| `hidden` | Should the script be visible in admin-site UI? `true` or `false`. Defaults to `false` | Optional |
| `security` | Should the script be shown in 'Sikkerhedsscripts' in admin-site UI? `true` or `false`. Defaults to `false` | Optional |
| `uid` | Special scripts that the admin-site needs to reference can be given an uid. <br> The uid *must* be unique, which also implies that only one version can be present in admin-site at any given time. `string`. Defaults to `null` | Optional |

0 comments on commit ca5bb7c

Please sign in to comment.