Installation
Requirements, installation and initial setup of the oPBWeb stack
Audience: Technical administration
Overview
oPBWeb runs as a Docker Compose stack on a Linux host that can reach the opsi configserver. The stack consists of these services:
| Service | Purpose |
|---|---|
| frontend | nginx serving the web interface and this manual; the only service exposed to the outside |
| api | REST API (FastAPI), sign-in, database migrations |
| worker | Background jobs: build, install, depot sync, connection to the opsi server |
| db | MariaDB for all application data |
| redis | Job queue and status information |
| garage | S3-compatible object storage for package files and built packages |
Technical administration performs the installation: prepare the host, create the configuration and secrets, start the stack. The subsequent initial setup in the interface (opsi server, depots, users) is done by a user with the Administrator role.
Chapters
- Requirements – host, Docker, ports, network to the configserver, opsi-side preparation and versions.
- Installation
– get the sources, create
.envand secrets, add the TLS certificate, start and check the stack. - Initial Setup – first sign-in, set up the configservers, set depot stages, create the first users.
- Test Environment – try oPBWeb without an opsi server, with two opsi mocks as config servers Test and Production.
For configuration, LDAP, operation and backup during ongoing operation, see Technical Administration .