User Guide

Create, edit, build and distribute packages

Roles: Viewer, Packager, Releaser, Administrator

Overview

The user guide describes your daily work with oPBWeb: creating or importing packages, editing control data and scripts, building packages and distributing them to the depots of your opsi config servers, from the test stage through to production. It also covers the Snippets, Depots and Jobs areas and the settings for your own account.

What you can use depends on your role. oPBWeb hides or disables buttons your role does not allow. The server checks every action as well.

Roles

The roles build on each other: each role has all permissions of the role before it. You can see your role in the avatar menu at the top right, below your name.

Role	What you can do
Viewer	View everything except Users and roles and Settings: package list, package editor (read only), source, snippets, jobs, depots, system status. Download built `.opsi` and `.md5` files.
Packager	Additionally create, import and edit packages, build, create new versions, delete versions, maintain your own snippets, sync depots, compare with the workbench. Install, uninstall and promote packages on depots of the Test and Staging stages.
Releaser	Additionally install, uninstall and promote packages on depots of the Production stage.
Administrator	Additionally users, config servers, settings, stages of config servers and depots, global snippets and storage cleanup. See Functional Administration .

Depot stages

oPBWeb can manage several opsi config servers. Each config server has a stage: Production, Staging or Test. Its depots inherit this stage unless an administrator sets a stage of their own for a depot; new config servers start in Production. The stage decides who may install, uninstall, promote packages, unlock locked products and delete repository files on the depot:

Stage	Required role
Test	Packager or higher
Staging	Packager or higher
Production	Releaser or higher

In the install dialog, depots your role is not sufficient for are marked “requires releaser role” and cannot be selected. With Promote … you take a tested version unchanged from one stage to the next, see Promoting to another stage .

Package lifecycle

Every package version is either Draft or Released:

Draft: A new, imported or copied version is a draft. You can edit it as you like.
Build: Build creates the .opsi file. The version stays a draft, and you can rebuild it as often as you like. If you change something afterwards, oPBWeb shows “changed since build”.
Installing releases: With Install … you distribute the current build to depots. This releases the version and makes it read-only.
Promote: With Promote … you take the tested, released version (the same build) to the depots of the next stage, for example from Test to Staging and then to Production.
Continue working: To make changes, create a New version (editable copy with a new version number) or set the version Back to draft (same version number).

For details, see Build and deploy .

Chapters

Getting Started – sign-in, interface layout, search
Packages – package list, new packages, import, meta packages
Package Editor – control data, dependencies, properties, changelog
Package Files – file tree, upload, MSI information, structure
Script Editor – edit opsi-script with completion, help and checks
Build and Deploy – build, install, uninstall, release, promote to other stages
Snippets – create, insert and import text snippets
Depots – config servers and depots, installed products, files, repository, comparison
Jobs – follow running and finished jobs
Account and Language – default language, password, sign-out