You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@
4
4
5
5
This project demonstrates a **proof of concept** for using a custom JupyterLab plugin to connect to a **remote Jupyter server's kernel manager** using a shared token. It shows how one JupyterLab frontend (Server B) can start and interact with kernels running on another backend Jupyter server (Server A).
6
6
7
+

8
+
7
9
---
8
10
9
11
## 🧩 What This Demo Does
@@ -52,6 +54,8 @@ Then open your browser at **http://localhost:8889/lab**. The kernel plugin will
52
54
53
55
You can confirm the kernel was created by checking **http://localhost:8888/api/kernels**.
54
56
57
+
💡 If prompted for a token in the browser, enter: abc123
58
+
55
59
## 🐳 Run with Docker
56
60
57
61
This project comes with a ready-to-use Docker and Docker Compose setup.
@@ -68,6 +72,8 @@ This launches:
68
72
-**http://localhost:8888** → Server A (backend kernel server)
69
73
-**http://localhost:8889** → Server B (JupyterLab frontend with plugin)
70
74
75
+
💡 If prompted for a token in the browser, enter: abc123
76
+
71
77
After going to **http://localhost:8889/lab**, Server B will start a kernel on Server A when loaded and you can see it in **http://localhost:8888/api/kernels**.
0 commit comments