Installation on oPBWeb Manual

Requirements

Mon, 01 Jan 0001 00:00:00 +0000

Audience: Technical administration

Overview

This chapter lists everything that must be in place before the installation: a Docker host, free ports, a network connection to the opsi configserver and a technical opsi user. Check the items in order before you start the Installation .

Host

oPBWeb runs on any Linux host with Docker. You can run the stack directly on the opsi configserver or on a separate host that reaches the configserver via HTTPS.

Installation

Mon, 01 Jan 0001 00:00:00 +0000

Audience: Technical administration

Overview

The installation takes only a few steps: get the sources, run ./setup-opbweb.sh (it writes the configuration file .env and generates the secrets), optionally add a TLS certificate, and start the stack. You either build the images locally with ./start.sh --build or pull prebuilt images from a registry. Then check that all services are running and continue with the Initial Setup in the interface.

Run all commands in the project directory on the Docker host. Check the Requirements first.

Initial Setup

Mon, 01 Jan 0001 00:00:00 +0000

Role: Administrator

Overview

After the Installation , oPBWeb is reachable but does not know any opsi server yet and has only one account: the first administrator. During the initial setup you sign in with this account, change its password, connect oPBWeb to one or more opsi configservers, define the depot stages and set up the first users.

For this you need the admin password from secrets/admin_password.txt, the credentials of the technical opsi user and shell access to the configserver to verify the fingerprint of the CA certificate.

Test Environment

Mon, 01 Jan 0001 00:00:00 +0000

Audience: Technical administration, anyone who wants to try oPBWeb

Overview

The test environment starts oPBWeb together with two simulated opsi servers (opsiconfd mocks). With them you try the editor and the whole workflow, from the import from the workbench through building to promoting from Test to Production, without a real opsi server.

Config server in oPBWeb	Stage	Depots	Mock container
`opsi-test`	Test	`opsi-test.mock` (config server), `depot-test.mock`	`opbweb-opsi-mock-test`
`opsi-prod`	Production	`opsi-prod.mock` (config server), `depot-prod.mock`	`opbweb-opsi-mock-prod`

The mocks run with the oPBWeb backend image, their code comes from tools/opsi-mock/opsi_mock.py. Both are part of the repository clone and of the stack ZIP . The short version of this guide is next to them as START-TEST-ENVIRONMENT_en.md.