Self-HostingConfiguration

Configuration

Self-hosted BioNodulo is configured through environment variables and an optional config file. This page lists the most common settings.

Core environment variables

VariableDefaultDescription
BIONODULO_SECRET_KEYRequired. Signing key for sessions/tokens.
BIONODULO_DATA_DIR/dataWhere workflows, caches, and outputs live.
BIONODULO_PORT8080HTTP port for the editor.
BIONODULO_LOG_LEVELinfodebug / info / warn / error.
BIONODULO_MAX_RAMhost memoryCap RAM available to node execution.
BIONODULO_MAX_CONCURRENCYCPU countMax nodes running in parallel.

Storage

By default everything lives under BIONODULO_DATA_DIR. To use object storage for artifacts:

VariableDescription
BIONODULO_S3_ENDPOINTS3-compatible endpoint URL
BIONODULO_S3_BUCKETBucket for outputs/artifacts
BIONODULO_S3_REGIONRegion
BIONODULO_S3_KEY / BIONODULO_S3_SECRETCredentials

Node execution backend

VariableDefaultDescription
BIONODULO_RUNNERdockerdocker, local, or slurm/k8s
BIONODULO_DOCKER_SOCK/var/run/docker.sockPath to the container socket.

For HPC, set BIONODULO_RUNNER=slurm to submit each node as a scheduler job.

Authentication

Self-hosted instances support local accounts out of the box. OIDC/SAML SSO is available for institutional deployments:

VariableDescription
BIONODULO_OIDC_ISSUEROIDC issuer URL
BIONODULO_OIDC_CLIENT_ID / _SECRETOIDC client creds

Next