Self-Hosted Gitlab

AI Workbench currently supports a self-hosted Gitlab.com integration for accessing private repositories, container images, and the ability to publish Projects to your self-hosted server.

You can use both an OAuth flow or Personal Access Token with self-hosted servers. To use OAuth, an administrator must first configure the OAuth app in the Gitlab server. To use a PAT, you only need to specify the server’s URL.

Follow these steps to create an OAuth2 application:

1. Follow these instructions to create the OAuth2 application

2. Set the RedirectURL to http://localhost:9999/callback

3. Set the Scopes to api

4. Save the Client ID and Client Secret values. These are needed by users to add the integration.

1. Create a new custom integration.

2. Select gitlab as the type

3. Enter the hostname of the self-hosted gitlab instance

4. Enter the OAuth2 Client ID from the step above

5. Enter the OAuth2 Client Secret from the step above

This will then add the Integration so you can “connect” to it.

When creating the integration, a file is written containing the integration information. You can distribute this file to users, and if they place it in the appropriate location, they will be able to connect to the server without having to manually add the integration first (and enter the Client ID/Secret ID values)

• macOS/Linux: ~/.nvwb/integrations/<integration-name>-integration.json

• Windows: C:\Users\<username>\AppData\Local\NVIDIA Corporation\AI Workbench\integrations\<integration-name>-integration.json

The self-hosted Gitlab server must use HTTPS.

If using a self-signed certificate ensure it is installed as a trusted root CA on any machine that AI Workbench will run on, including remote locations.