Skip to content

Server management #15

@seeM

Description

@seeM

With Jupyter, each server is a separate browser tab, which would be the equivalent to a separate window for us. In this case we'd also need a login screen. Jupyter Desktop might have some interesting approaches here.

VSCode handles both server management and session management (#14) differently than Jupyter. For each open notebook file you decide on the server (or local kernel) and kernel spec.

Which UX is better? How can we decide? I'm more familiar with the Jupyter approach. It feels more transparent, but that might just be my familiarity (and the fact that VSCode kernels always irrecoverably crash on me).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions