Administer Javo

Javo is configured through the values of its Helm chart (the Docker Compose install uses the same chart). Change a value, then helm upgrade the release.

• Configuration: how values are organised, and the ones most installs set.
• Sign-in and roles: local accounts, OpenID Connect (Keycloak and others), groups to roles.
• App addresses: path or subdomain, and why sharing wants a separate host.
• Sizes: CPU, memory and GPU sizes, and custom amounts.
• Idle stop: stop apps nobody uses.
• Storage: home folders, group folders and scratch space.
• Backups and restore: database copies, home folders, an S3 bucket.
• Secrets and keys: the key that protects people’s secrets.
• AI: connect a model.
• Nebi environments (optional).
• App thumbnails (optional).
• Branding: your own name, logo, favicon and accent colour.
• Upgrades.
• Migrating from the data science pack: bring JupyterHub home folders over.

Platform admins also get these tabs under Settings: All apps (every person’s apps, with a Stop button that tells the owner an admin stopped it), Usage (app-hours by person or group over 7 or 30 days), Backups and Storage.