# Git and registry credentials

> Deploy from private Git repositories and private image registries.

Source: https://quasar.achaverot.fr/docs/server/credentials/

## Git credentials

To deploy a private repository, add a token in **Settings → Git credentials**. The page links to where each forge creates tokens, and which permissions they need.

### Scopes

Each token has a **scope**, which decides which repositories it is used for:

| Scope | Matches |
| --- | --- |
| `github.com` | Every repository on that forge. |
| `github.com/acme` | Every repository of that organisation or user. |
| `github.com/acme/app` | That repository only. |
| `*` | Any repository, as a fallback. |

When several tokens match, **the most specific one is used**. This lets a personal account and a work organisation each have their own token.

Scopes are compared segment by segment: `github.com/acme` never matches `github.com/acmecorp`.

### Good to know

- Tokens are encrypted, and never shown again after saving.
- **Test** checks a token against a real repository.
- Each token lists the applications that use it.

## Image registries

To deploy images from a private registry, add it in **Settings → Image registries**:

| Field | Example |
| --- | --- |
| Server | `ghcr.io`, or `docker.io` for private Docker Hub images |
| Username | Your account name |
| Token / password | An access token |

The credentials are used automatically for images whose name starts with that server. Public images need nothing.