Settings

Project settings can be managed from the "Settings" tab in the project dashboard. The settings page has three tabs: General, Files, and Servers.

General Settings

General settings are used to manage project display and configuration.

Project Settings

• Name: This is the name of the project displayed in the Cloud Console and on the public releases page.
• Primary File: This is the file that launched from the "Launch Primary File" button in the project dashboard.
• Version: This is the version of the project.
• Description: This description is displayed in the project dashboard and can be used to store information, external links, etc.
• Private Releases: This is a boolean that determines if the project releases are private or public by default. Toggle this off if you want to automatically make new releases publish to the releases page.
• Publish on Release: Configure publish destinations that are used when a release is created. When you promote a release candidate to a full release, the build will be automatically published to the destinations configured here.

Build Settings

These are the default build settings for your project. Use this section to manage what happens when a release candidate is created. They can be changed at the time of release candidate creation, but we recommend setting them here to make life smoother.

Publish destinations allow you to automatically move a newly created release candidate to another server or other publish destination as you wish. These can only be set up in the build settings, not when running a release candidate.

Project Deletion

If you need to delete a project for some reason, you can do so here. Note: This will delete all data associated with the project, including checkpoints, builds, releases, and deployments.

File Settings

In the Files tab you can manage the files connected to your project as well as their credentials. This tab has two sections, Default and Server specific.

Default Settings

In the default settings you can set file credentials, notes, and optionally exclude a file from checkpoints.

• Credentials: These are Full Access credentials for the file. The credentials are used to run checkpoints on the file. If you want to use a different set of credentials when running a deployment (coming soon), you can choose to use a different set of credentials here.
• Notes: Add notes about the file to display in the Files section of the project dashboard.
• Exclude From Checkpoints: If toggled, the file will not be included in checkpoints. This is useful if you have a file that does not change over time but you still need to include in builds or if you have a file that is large and you don't want to checkpoint it.

You can also add and remove files from this screen. New files will not display any changes in the first checkpoint they are added to as we create a baseline to compare against. Removed files will no longer appear in subsequent checkpoints.

Server Specific Settings

Server specific settings are used to manage the credentials for a specific server. You can override the file name or credentials on specific servers so that you can properly launch the file in the project dashboard.

Server Settings

In the Servers tab you can manage the servers connected to your project. For now the make reason to have multiple servers is for ease of launching files across different servers, but we plan to integrate the server connection into the deployment process in the Cloud Console in the future.