This part of the documentation is only intended in the context of a supported PoC (Proof of Concept) together with the Steadybit team. Please, book an appointment to scope your PoC before continuing to evaluate the on-prem solution.
The machine you are installing steadybit onto, must have at least 4 CPUs and 8 GB available memory.
The platform docker image doesn't contain any shell by default. In case you need to exec into the container using a shell for debugging purposes, we provide an additional debug variant whith the
Steadybit requires a PostgresSQL 13 database.
For running the platform with multiple instances, a Redis message broker is required.
You can use a static username/password to authenticate as an admin user
You can use a LDAP Server for user authentication.
By default the ldap is accessed anonymously, unless
STEADYBIT_AUTH_LDAP_MANAGER_PASSWORDis set. The users are authenticated by doing a bind with their credentials, unless
STEADYBIT_AUTH_LDAP_METHODis set to
You can use an OpenID Connect compatible authentication provider for user authentication. Steadybit uses the
The first user to login will be assigned the
ADMINrole, all other will be assigned the
USERrole. The roles can be changed by an admin user via the UI.
SSL can be configured by setting the various
SERVER_SSL_*properties and requires a java keystore (typically PKCS12).
Steadybit will use these proxy settings if the platform needs to connect to other services (for example your OIDC identity provider).