Runtime Connections

Connecting to Sanbox Runtime with Designer

Lumisan Sanbox Designer requires you to connect to a Sanbox Runtime in order to operate. When connected, Sanbox Designer maintains a 2-way HTTP2 connection with the Runtime.

The Runtime Connection Manager window shows when a connection is not configured automatically and allows you to store connections to multiple Runtimes. You can also deploy images from the currently connected Runtime to another Runtime.

Not to be confused with Docker Images, visit the Runtime Architecture & Requirements page to learn about Runtime Images.

Runtime Connection Manager

Creating a Runtime Connection

Pressing the plus button at the bottom of the screen opens the Runtime Connection Editor.

Creating a Runtime Connection
  • Connection Name - The name of the connection as it shows in the Connection Manager.

  • Hostname/IP - Host name or IP Address to the Runtime you want to connect to.

  • Port - Port number to use. The default is 50155 which is also the default configuration on Sanbox Runtime.

  • Access ID - Access ID to use. Default is admin

  • Access Key - Access key for the specified Access ID. Default is admin

  • Secure Connection - When checked, indicates that the connection between the Designer and Runtime will be encrypted. Visit the Securing Designer Connections article to learn how to configure your Runtime for secure connections.

To learn what the Access ID and Access Key are used for, visit the Runtime Configuration article. Once you've created your connection, double-clicking it will have the Designer initiate the connection.

Deploying Images

Deploying an Image

Clicking the cloud icon for a Runtime while connected to another will pull up the Push Current Image screen, allowing you to deploy the image of the current Runtime to a target Runtime.

You must configure the Runtime to accept deployments and specify an API Key to use. Visit the Deployments article and follow the first section to set up this configuration for the Runtime. You can also follow the aforementioned article to set up automatic deployments that are part of your DevOps process.