Configuration
DVC Studio gets provisioned by Helm, which uses a single YAML file for
configuration, often referred to as values.yaml in our documentation.
To learn more about Helm's configuration format, refer to the page Values Files on the Helm website.
Updating the configuration
If you've deployed DVC Studio with the AMI, you'll need to SSH to the EC2 instance before continuing.
To update the configuration and apply the changes, follow the instructions below:
- Update DVC Studio's
values.yamlconfig file
Example: Updating the hostname
Merge the existing values.yaml file with the following contents:
global:
host: studio.company2.com- Reload DVC Studio
$ helm upgrade --wait studio iterative/studio --namespace studio -f values.yamlMore configuration options
The previous chapter provided a basic example of updating the DVC Studio configuration. In most cases, you'll likely need to do more configuration to set up DVC Studio to your needs.
To integrate DVC Studio with your Git forge (GitHub, GitLab, Bitbucket), see the Git Forges section.
To allow secure access to DVC Studio, we highly recommend setting up a valid TLS certificate. To set this up, check out the TLS certificates page.
If you use HTTPS to connect to your Studio instance, check out how to set up your SSL certificate.