Skip to content

[Notebook Migration] Migrate Jupyter server from prototype implementation to Texera back-end #4305

Closed as not planned

Description

@yunyad

Task Summary

Currently, the Jupyter server exists externally to the Texera backend because of the implementation used for initial prototyping. It is currently in a docker container that must be manually started by the developer. In order to fully implement the notebook migration tool as a Texera microservice, we will need to move the Jupyter server from outside of Texera to be managed by Texera.

Proposed Solution or Design

Now we will introduce a new microservice for the Jupyter server, which will communicate with the notebook migration microservice to provide the Jupyter UI in the Texera workspace. This microservice will introduce a new docker-compose yaml file that uses a public Jupyter image, in addition to new endpoints in the existing notebook-migration-service to communicate with the Jupyter server. The new endpoints include setting the notebook inside of Jupyter to allow the user to view and edit their original notebook, and retrieving the relevant URLs needed to render the Jupyter UI inside of an iframe.

Priority

P2 – Medium

Task Type

  • Code Implementation
  • Documentation
  • Refactor / Cleanup
  • Testing / QA
  • DevOps / Deployment

Activity

  1. added theissue type on Mar 17, 2026
  2. chenlica commented on Mar 18, 2026

    @chenlica
    Contributor

    @yunyad Please provide more details in the description.

  3. changed the title [-]Move Jupyter server to new microservice[/-] [+]Migrate Jupyter Server to Texera Backend[/+] on Mar 18, 2026
  4. changed the title [-]Migrate Jupyter Server to Texera Backend[/-] [+][Notebook Migration] Migrate Jupyter server from prototype implementation to Texera back-end[/+] on Mar 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions