Now organization admins/owner can go to Form Bench tab, and click “Create New” to create a new formbench app. It has to be a container.

See for field details

Choose the app to edit, you will be brought to a page similar to creating app page without the ability to modify app id.

See for field details

Unique id for your app. It is unique within organization. ID must start with a letter, and only has digits, letters and “_”, “-”.

Human friendly display name of the app.

Description of the app

Currently apps are divided into 5 types:

Reason for this field is that for some apps, especially jupyter apps, our backend need to add some run options for it to run properly and we don’t want to expose everything to the user.

Also it will be used to determine the app access.

Name and tag of the container you want to use. In the format of org/container:tag Default tag is latest. Currently we only support pulling pulling public containers from docker hub.

The port of your app

The mount point of your container.

Entry point command. If provided, will override the entry point of the container

Parameters you need to run the container properly. Usually it is everything after your container name in a docker run command.

Provide all your environment variables in a string, separate them using space.

GRANT_SUDO=yes MYENV=a

User to run the container.

Currently we have two types of app, one is “exploration”, like Rstudio, JupyterLab. They have “rw” access. The other is “visualization”, like rshiny apps, they have “ro” access.

By default, byo apps can only be used within the organization unless its visibility is set to “PUBLIC”.

Organization owner and admins can create, update, delete apps.

By default, all projects in the organization will be able to access the organization byo apps and all public apps. But different project roles have different access.

Table below shows which role can launch which app.

Currently support Nvidia T4, L4 and P100. When you enable GPU, 1 GPU will be used.