> For the complete documentation index, see [llms.txt](https://comunity.gitbook.io/learning.comunitynexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://comunity.gitbook.io/learning.comunitynexus/26.2/toolkit-guides/web-sites/configure-devops-repositories.md).

# Configure DevOps repositories

{% hint style="info" %}
**Toolkit administrator role required.** This page describes an option in the Toolkit administration menu, which manages settings for the platform installation as a whole. It is visible only when signed in with the **Toolkit administrator** role, and is separate from Project Settings.
{% endhint %}

Web sites can be created inside a DevOps repository, so that a site is developed and version-controlled like any other codebase. Where the repositories are created is defined once for the platform installation and inherited by every project, so that a developer creating a web site does not need to know anything about the underlying DevOps organisation.

## What the configuration defines

The configuration identifies a **DevOps project**, not an individual repository. A DevOps project contains a set of repositories, and the platform creates a new repository inside it each time a web site is created with the repository option selected.

Each repository is named from the project's **Application Name**, shown in Project Settings, and the web site URL suffix, joined by a hyphen.

## Where the configuration lives

Sign in with the **Toolkit administrator** role and open **DevOps repositories** in the **Toolkit administration** menu.

<figure><img src="/files/UtA3jCwwukMzeSLaQSHy" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/3l676F1Yqzm0QMpiXn7W" alt=""><figcaption></figcaption></figure>

\
The configuration is set once for the platform installation. It does not need revisiting unless the DevOps project changes.

## The access token

Creating repositories requires an access token obtained from DevOps and entered here.

{% hint style="info" %}
The token is never displayed again after it is saved. A replacement token can be supplied at any time, but the existing token cannot be viewed or edited. This is deliberate, because storing and displaying a credential is a security risk.
{% endhint %}

Supplying a replacement token is how a token is rotated, and how the configuration is pointed at a different DevOps project.

## Projects that override the default

The screen lists the projects that have replaced this configuration with one of their own. See [Set a project DevOps repository](/learning.comunitynexus/26.2/toolkit-guides/web-sites/set-a-project-devops-repository.md).

## Records requiring maintenance

Beneath the override list, the screen shows configuration records that are not correctly linked to a tenant or to a project. These are displayed as errors and can be removed from this screen. This is routine maintenance rather than a fault with the platform, and it is the reason this option carries more administrative upkeep than most.

## Disabling a configuration

A configuration can be disabled but not deleted.

Where no configuration is enabled for an environment, **Create DevOps repository** is unavailable when a web site is created. The web site is still created, complete with the helper library, but without version control. See [Create a web site](/learning.comunitynexus/26.2/toolkit-guides/web-sites/create-a-web-site.md).

## Where to go next

* [Set a project DevOps repository](/learning.comunitynexus/26.2/toolkit-guides/web-sites/set-a-project-devops-repository.md): give a single project a repository of its own
* [Create a web site](/learning.comunitynexus/26.2/toolkit-guides/web-sites/create-a-web-site.md): what a developer sees once this is configured