mengw15 commented on code in PR #7932:
URL: https://github.com/apache/texera/pull/7932#discussion_r3848471587
##########
bin/single-node/README.md:
##########
@@ -141,6 +142,27 @@ To switch providers or add more LLMs, see [Add more LLMs
or providers](#add-more
+## Use the notebook migration tool
+
+The notebook migration tool converts a Jupyter notebook into a Texera
workflow. It runs a JupyterLab
+server alongside Texera (published on port 9100) and embeds it in the
workspace. The conversion itself
+is powered by an LLM, so it needs an API key exactly like [the Texera
agent](#enable-the-texera-agent);
+without one the tool still appears but the conversion fails with a provider
auth error.
+
+The tool is enabled by default. To turn it off, set
`GUI_WORKFLOW_WORKSPACE_PYTHON_NOTEBOOK_MIGRATION_ENABLED=false`
+in the `.env` file.
+
+Once Texera is up, go to your workflow list and click the robot button ("AI
generate a workflow from a
+Python notebook"). Upload a `.ipynb` file and pick a model; Texera generates
the workflow and opens it.
+In the workspace, a Jupyter button then appears in the menu bar to expand the
notebook alongside the
+generated workflow.
+
+> ⚠️ All users share one JupyterLab server and one access token. Anyone who
can reach Texera sees the
Review Comment:
This is the only exposure warning in the README — there's nothing similar
for 8080 or 9000, even though 8080 with the default `texera`/`texera` admin
already gives you code execution via a Python UDF, and 9000 is MinIO on
`texera_minio`/`password`. Singling out 9100 implies those two are fine.
Probably simplest to drop it and keep the section consistent with the rest
of the file.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
