Private Git repositories
Access to private Git repositories can be managed from the Credentials section, accessible from the Credentials tab.
Tower provides support to connect to private repositories from the popular Git hosting platforms GitHub, GitLab, and BitBucket.
All credentials are securely stored using advanced encryption (AES-256) and never exposed by any Tower API.
To connect a private GitHub repository you need to enter a Name for the credentials, a Username and a Password or Access token.
It is recommended to use an access token instead of a using your password. Personal access tokens (PATs) are an alternative to using passwords for authentication to GitHub when using APIs. Step-by-step instructions to create a personal access token can be found here.
To connect a private GitLab repository you need to enter a Name for the credentials, a Username, Password and Access token.
A GitLab API access token that can be found in your GitLab account page. Make sure to select the
To connect a private BitBucket repository you need to enter a Name for the credentials, a Username and a BitBucket App password.
This step-by-step example shows how to create a BitBucket App password.
It is also possible to specify Git server endpoints for private hosting.
These can be specified in a file
tower.yaml and must be accessible from the backend and cron container instances.
1 2 3 4 5 6 7 8 9
For more details on this configuration, see the Nextflow SCM configuration file for examples. You can first test your connection with a Nextflow execution using the standard SCM file and then convert it to the YAML structure, as shown above, for Tower.