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
I thought, perhaps - when specifying the URL, http://localhost:50773/server:namespace?token=1 couldn't the user be walked through constructing the URL (choosing the server from the configured server manager list, and subsequent namespaces already defined)
prompt for JupyterProxy server (default localhost)
prompt for JupyterProxy server port (default 50773)
choose target server (list built from Intersystemsm Server manager)
choose namespace (list built based on IRIS instance chosen)
specify friendly name for this configuration,,
steve
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. Because of how this extension leverages VS Code's Jupyter support rather than implementing its own infrastructure I don't think it'll be possible to do exactly what you suggest. However #6 proposes we take advantage of a recently-finalized API in the Jupyter extension to streamline this part of the UX.
I thought, perhaps - when specifying the URL, http://localhost:50773/server:namespace?token=1 couldn't the user be walked through constructing the URL (choosing the server from the configured server manager list, and subsequent namespaces already defined)
prompt for JupyterProxy server (default localhost)
prompt for JupyterProxy server port (default 50773)
choose target server (list built from Intersystemsm Server manager)
choose namespace (list built based on IRIS instance chosen)
specify friendly name for this configuration,,
steve
The text was updated successfully, but these errors were encountered: