[PR #1431] [MERGED] docs: fix the Jupyter tutorial's Compose indentation and release link, and explain the auth modes and per-run kernels #1395

New issue

Closed

opened 2026-10-18 14:19:22 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:19:22 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/1431
Author: @silentoplayz
Created: 9/18/2026
Status: ✅ Merged
Merged: 9/26/2026
Merged by: @silentoplayz

Base: main ← Head: docs/jupyter-tutorial

📝 Commits (1)

2adb6c5 docs: fix the Jupyter tutorial's Compose indentation and release link, and explain the auth modes and per-run kernels

📊 Changes

1 file changed (+28 additions, -22 deletions)

View changed files

📝 docs/tutorials/integrations/dev-tools/jupyter.md (+28 -22)

📄 Description

Summary

The Jupyter tutorial's Compose example had every key flush left, so it was not valid YAML. It is re-indented, with the extra_hosts entry that makes host.docker.internal resolve on Linux. The Open WebUI v0.5.15 release link pointed at v0.5.14. The settings table now says these are persisted admin settings seeded once from the environment, that CODE_EXECUTION_JUPYTER_AUTH accepts exactly token or password, and that the CODE_INTERPRETER_JUPYTER_* variables default to their CODE_EXECUTION_JUPYTER_* twins while CODE_INTERPRETER_ENGINE defaults to pyodide, so both engine variables need setting. The workflow note explains why nothing persists between runs. Each execution starts a fresh kernel and deletes it afterwards.

None.

Checklist

I have reviewed the relevant documentation and matched the existing style.
This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility.
I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories.

Notes for reviewers

Sources on dev: routers/utils.py and utils/code_interpreter.py (auth modes, kernel lifecycle), routers/configs.py (CODE_EXECUTION_CONFIG_KEYS), config.py (the CODE_INTERPRETER_* fallbacks), and CHANGELOG.md for v0.5.15.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/docs/pull/1431 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 9/18/2026 **Status:** ✅ Merged **Merged:** 9/26/2026 **Merged by:** [@silentoplayz](https://github.com/silentoplayz) **Base:** `main` ← **Head:** `docs/jupyter-tutorial` --- ### 📝 Commits (1) - [`2adb6c5`](https://github.com/open-webui/docs/commit/2adb6c5791736cf9a4760e0fa49367450b892842) docs: fix the Jupyter tutorial's Compose indentation and release link, and explain the auth modes and per-run kernels ### 📊 Changes **1 file changed** (+28 additions, -22 deletions) <details> <summary>View changed files</summary> 📝 `docs/tutorials/integrations/dev-tools/jupyter.md` (+28 -22) </details> ### 📄 Description ## Summary The Jupyter tutorial's Compose example had every key flush left, so it was not valid YAML. It is re-indented, with the `extra_hosts` entry that makes `host.docker.internal` resolve on Linux. The Open WebUI v0.5.15 release link pointed at v0.5.14. The settings table now says these are persisted admin settings seeded once from the environment, that `CODE_EXECUTION_JUPYTER_AUTH` accepts exactly `token` or `password`, and that the `CODE_INTERPRETER_JUPYTER_*` variables default to their `CODE_EXECUTION_JUPYTER_*` twins while `CODE_INTERPRETER_ENGINE` defaults to `pyodide`, so both engine variables need setting. The workflow note explains why nothing persists between runs. Each execution starts a fresh kernel and deletes it afterwards. ## Related issue or discussion None. ## Checklist - [x] I have reviewed the relevant documentation and matched the existing style. - [x] This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility. - [x] I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories. ## Notes for reviewers Sources on `dev`: `routers/utils.py` and `utils/code_interpreter.py` (auth modes, kernel lifecycle), `routers/configs.py` (`CODE_EXECUTION_CONFIG_KEYS`), `config.py` (the `CODE_INTERPRETER_*` fallbacks), and `CHANGELOG.md` for v0.5.15. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:19:22 +00:00