domino logo
Tech Ecosystem
Get started with Python
Step 0: Orient yourself to DominoStep 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get started with R
Step 0: Orient yourself to Domino (R Tutorial)Step 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get Started with MATLAB
Step 1: Orient yourself to DominoStep 2: Create a Domino ProjectStep 3: Configure Your Domino ProjectStep 4: Start a MATLAB WorkspaceStep 5: Fetch and Save Your DataStep 6: Develop Your ModelStep 7: Clean Up Your Workspace
Step 8: Deploy Your Model
Scheduled JobsLaunchers
Step 9: Working with Domino Datasets
Domino Reference
Projects
Projects Overview
Revert Projects and Files
Revert a ProjectRevert a File
Projects PortfolioProject Goals in Domino 4+Jira Integration in DominoUpload Files to Domino using your BrowserFork and Merge ProjectsSearchSharing and CollaborationCommentsDomino Service FilesystemCompare File RevisionsArchive a Project
Advanced Project Settings
Project DependenciesProject TagsRename a ProjectSet up your Project to Ignore FilesUpload files larger than 550MBExporting Files as a Python or R PackageTransfer Project Ownership
Domino Runs
JobsDiagnostic Statistics with dominostats.jsonNotificationsResultsRun Comparison
Advanced Options for Domino Runs
Run StatesDomino Environment VariablesEnvironment Variables for Secure Credential StorageUse Apache Airflow with Domino
Scheduled Jobs
Domino Workspaces
WorkspacesUse Visual Studio Code in Domino WorkspacesPersist RStudio PreferencesAccess Multiple Hosted Applications in one Workspace SessionUse Domino Workspaces in Safari
Spark on Domino
On-Demand Spark
On-Demand Spark OverviewValidated Spark VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
External Hadoop and Spark
Hadoop and Spark OverviewConnect to a Cloudera CDH5 cluster from DominoConnect to a Hortonworks cluster from DominoConnect to a MapR cluster from DominoConnect to an Amazon EMR cluster from DominoRun Local Spark on a Domino ExecutorUse PySpark in Jupyter WorkspacesKerberos Authentication
Customize the Domino Software Environment
Environment ManagementDomino Standard EnvironmentsInstall Packages and DependenciesAdd Workspace IDEs
Advanced Options for Domino Software Environment
Install Custom Packages in Domino with Git IntegrationAdd Custom DNS Servers to Your Domino EnvironmentConfigure a Compute Environment to User Private Cran/Conda/PyPi MirrorsScala notebooksUse TensorBoard in Jupyter WorkspacesUse MATLAB as a WorkspaceCreate a SAS Data Science Workspace Environment
Publish your Work
Publish a Model API
Model Publishing OverviewModel Invocation SettingsModel Access and CollaborationModel Deployment ConfigurationPromote Projects to ProductionExport Model Image
Publish a Web Application
Cross-Origin Security in Domino web appsApp Publishing OverviewGet Started with DashGet Started with ShinyGet Started with Flask
Advanced Web Application Settings in Domino
App Scaling and PerformanceHost HTML Pages from DominoHow to Get the Domino Username of an App Viewer
Launchers
Launchers OverviewAdvanced Launcher Editor
Assets Portfolio Overview
Connect to your Data
Domino Datasets
Datasets OverviewDatasets Best PracticesAbout domino.yamlDatasets Advanced Mode TutorialDatasets Scratch SpacesConvert Legacy Data Sets to Domino Datasets
Data Sources Overview
Connect to Data Sources
External Data Volumes
Git and Domino
Git Repositories in DominoWork From a Commit ID in Git
Work with Data Best Practices
Work with Big Data in DominoWork with Lots of FilesMove Data Over a Network
Advanced User Configuration Settings
User API KeysDomino TokenOrganizations Overview
Use the Domino Command Line Interface (CLI)
Install the Domino Command Line (CLI)Domino CLI ReferenceDownload Files with the CLIForce-Restore a Local ProjectMove a Project Between Domino DeploymentsUse the Domino CLI Behind a Proxy
Browser Support
Get Help with Domino
Additional ResourcesGet Domino VersionContact Domino Technical SupportSupport Bundles
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
User Guide
>
Domino Reference
>
Domino Workspaces
>
Access Multiple Hosted Applications in one Workspace Session

Access Multiple Hosted Applications in one Workspace Session

For security reasons, Domino Workspace sessions are only accessible on one port. For example, Jupyter typically uses port 8888. When you launch a Jupyter Workspace session, a Domino executor starts the Jupyter server in a Run, and opens port 8888 to serve the Jupyter application to your browser. If you were to try to use the Jupyter terminal to start another application on a different port, it would not be accessible.

However, in some cases you might want to run multiple interactive applications in the same Workspace session. These cases include:

  • Editing and debugging Dash or Flask apps live

  • Using Tensorboard to view progress of a live training job

Domino 3.5+ supports this with Jupyter Server Proxy and JupyterLab.

Prerequisites

  • Python 3+

  • Jupyter Server Proxy

Jupyter Server Proxy is installed by default in the latest Domino Standard Environments. To install it in one of your existing environments, see the following instructions.

Install Jupyter Server Proxy in your environment

If you are not on the recent version of the Domino Standard Environment, you can use the following steps to install Jupyter Server Proxy in your Domino Environment.

  1. Add the following lines to your environment’s Dockerfile Instructions.

    # Install NodeJS
    # You can omit this step if your environment already has NodeJS 6+ installed
    RUN curl -sL https://deb.nodesource.com/setup_8.x | bash - && \
    apt-get install nodejs -y && \
    rm -rf /var/lib/apt/lists/*
    
    # Switch to the latest JupyterLab start script
    RUN rm -rf /var/opt/workspaces/Jupyterlab/start.sh && \
    cd /var/opt/workspaces/Jupyterlab/ && \
    wget https://raw.githubusercontent.com/dominodatalab/workspace-configs/2019q4-v1/Jupyterlab/start.sh && \
    chmod 777 /var/opt/workspaces/Jupyterlab/start.sh
    
    # Install and enable jupyter-server-proxy
    RUN pip install --upgrade jupyterlab==0.35.4 && \
    pip install nbserverproxy jupyter-server-proxy && \
    jupyter serverextension enable --py --sys-prefix nbserverproxy && \
    jupyter labextension install jupyterlab-server-proxy
  2. Update the JupyterLab definition in the Pluggable Workspace Tools section of your environment.

    jupyterlab:
       title: "JupyterLab (Beta)"
       iconUrl: "/assets/images/workspace-logos/jupyterlab.svg"
       start: [ /var/opt/workspaces/Jupyterlab/start.sh ]
       httpProxy:
       internalPath: "/{{ownerUsername}}/{{projectName}}/{{sessionPathComponent}}/{{runId}}/{{#if pathToOpen}}tree/{{pathToOpen}}{{/if}}"
       port: 8888
       rewrite: false
       requireSubdomain: false

Use Jupyter Server Proxy

If you launch a JupyterLab Workspace session in an environment with Jupyter Server Proxy installed, you can start and serve additional applications if they are served on a different port than JupyterLab.

Once an additional application is started, you can access it at the following URI:

Suppose your JupyterLab session is served at:

`https://<YourDominoURL>/workspace?owner=<ownername>&projectName=<projectname>&runId=<runhash>'

If you then use the JupyterLab terminal to start a Dash app on port 8887 for debugging, you could open the Dash app at:

https://<YourDominoURL>/owner=<ownername>/projectName=<projectname>/notebookSession/runid=<runhash>/proxy/8887/*

If you instead use the JupyterLab terminal to start a Bokeh app on port 5006, you could open the Bokeh app at:

https://<YourDominoURL>/owner=<ownername>/projectName=<projectname>/notebookSession/runid=<runhash>/proxy/5006/

With this model you can host multiple applications on different ports and expose each through your JupyterLab workspace.

jupyterlab new tile

If you edit the source files in JupyterLab after the application is running, you must restart the app in the browser for the edits will take effect.

For environments that have VSCode installed in JupyterLab, you can start a VSCode session from JupyterLab, and then start an App from VSCode. This allows you to debug using VSCode.

A new App or process that you start and open in a separate tab will not have the Domino Workspace with options to stop, sync, commit, or manage your project files. To access this application and manage your changes, you must open the main JupyterLab tab for your Workspace session.

Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.