Skip to content

Commit e5e43dc

Browse files
Merge pull request #3 from Meriem-BenIsmail/readme
README
2 parents a372e97 + 3098c69 commit e5e43dc

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44

55
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).
66

7+
![Demo](demo.gif)
8+
79
---
810

911
## 🧩 What This Demo Does
@@ -52,6 +54,8 @@ Then open your browser at **http://localhost:8889/lab**. The kernel plugin will
5254

5355
You can confirm the kernel was created by checking **http://localhost:8888/api/kernels**.
5456

57+
💡 If prompted for a token in the browser, enter: abc123
58+
5559
## 🐳 Run with Docker
5660

5761
This project comes with a ready-to-use Docker and Docker Compose setup.
@@ -68,6 +72,8 @@ This launches:
6872
- **http://localhost:8888** → Server A (backend kernel server)
6973
- **http://localhost:8889** → Server B (JupyterLab frontend with plugin)
7074

75+
💡 If prompted for a token in the browser, enter: abc123
76+
7177
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**.
7278

7379
## 💡 Notes

demo.gif

2.72 MB
Loading

0 commit comments

Comments
 (0)