GitLab Environment — Access Tokens

Access tokens let Git, CI runners, and tools authenticate to git.nexus-cloud.uk without using your account password.

Personal Access Token (HTTPS)

1. Sign in to git.nexus-cloud.uk
2. Click your avatar → Preferences → Access Tokens
3. Create a token with a name and expiry date
4. Enable scopes:
   • read_repository — clone and pull
   • write_repository — push code
   • api — if tools need the GitLab API
5. Copy the token immediately — it is shown only once

Use the token as the password when Git prompts over HTTPS:

git clone https://git.nexus-cloud.uk/your-group/your-project.git
# Username: your_gitlab_username
# Password: glpat-xxxxxxxxxxxx

Store tokens in a password manager. Do not commit tokens to repositories.

SSH keys (recommended for daily dev)

1. Generate a key (if you do not have one):

ssh-keygen -t ed25519 -C "you@example.com"

2. Copy the public key (~/.ssh/id_ed25519.pub)
3. GitLab → Preferences → SSH Keys → paste and save
4. Clone with SSH URLs (git@git.nexus-cloud.uk:group/project.git)

CI/CD variables

For pipelines that deploy to game servers, store secrets in Settings → CI/CD → Variables:

• Mark sensitive values as Masked and Protected
• Use File type for SSH private keys where needed

Never hard-code passwords or API keys in .gitlab-ci.yml.

Revoking access

Delete unused tokens and remove SSH keys from GitLab when a developer leaves the team.