Configuring a Server

Server configuration is available from the Configure tab on the server dashboard.

To get there:

1. Select the Infrastructure tab from the main, left-hand navigation.
2. Click into Servers from the infrastructure sub-menu.
3. Use links on the dashboard or the main dropdown to select a server.
4. Select Configure from the horizontal navigation.

Reconfigure Server

At the top of the page, users can interact with configuration options and then reconfigure the server using the button. These reconfigure events do not cause servers to restart.

Allow SFTP

Container instance volumes with remote access enabled require the underlying server to be configured to allow SFTP connections.

To enable SFTP connections on the server select the checkbox to enable, and click the Reconfigure Server button.

Custom Base Volume Size

A base volume is how much space should be set aside for images on this server. If a user wishes to increase this amount they can using this form.

Gateway

With the launch of virtual machine support, the server configure page now supports gateway settings.

By enabling gateway, the server is marked as available for gateway services to be deployed to it. While the Type dropdown shows two options, during the beta only Static is implemented and available.

In the future users will be able to set BGP only at providers which support this natively. Those providers will be listed here.

Shared Mounts

The shared mounts option is meant for users that wish to mount a file system that is remote to the host it will be mounted on.

The first step in creating a shared mount is to enter an identifier and press the + button.

• Type - The filesystem type.
• Options - Filesystem mount options.
• Source - Where is the source of the data?

example for an NFS mount through EFS on AWS.

• type - nfs4
• options - nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,addr=ip address
• source - :/

Shared Directories

The shared directories option is a much simpler form. Shared directories only require an identifier and each entry represents a directory on the host that can be consumed by any container.