> ## Documentation Index
> Fetch the complete documentation index at: https://deployment.naudecoreventures.com/llms.txt
> Use this file to discover all available pages before exploring further.

# NCV GitLab Delivery Platform

> How NCV deploys, operates, and develops on code.naudecoreventures.com â€” implementation, operations, CI/CD, migration, and go-live gates.

# NCV GitLab Delivery Platform

**Platform:** `https://code.naudecoreventures.com` Â· **Registry:** `https://registry.code.naudecoreventures.com`

This site is the operating documentation for the NCV engineering delivery platform: how it is
implemented, administered, and secured; how developers work in it; how repositories migrate
from Azure DevOps; how build and release pipelines behave; and what must pass before go-live.

## Platform at a glance

* **GitLab Self-Managed EE** on Ubuntu 24.04 LTS, installed from GitLab's official Linux package, running the Free feature set on the target Hetzner host.
* Hosts: private Git repositories, merge requests and code review, CI/CD control plane, Generic Package Registry (EXE/ZIP/AppImage/DEB/RPM release artifacts), Container Registry, Releases and release notes, Jira integration, and one tightly limited Linux Docker runner for low-volume CI.
* Separate machines or hosted services carry what the main host must not: the Windows runner (native Flutter Windows builds, EXE/MSIX/Inno packaging, Windows signing), the macOS runner (iOS/macOS builds, Xcode signing, TestFlight, App Store Connect), and two offsite backup repositories (application data and configuration/decryption secrets encrypted separately, because RAID 1 is not a backup).
* **Jira Cloud remains the work-management source of truth.** Azure Boards are not migrated into GitLab.
* Server posture: **GitLab first, runner second.** The co-located runner starts with `concurrent = 1`, a two-CPU limit, and an 8 GB memory limit. The first month is a measured pilot â€” if p95 web latency, Sidekiq backlog, load average, or runner queueing crosses the thresholds in the operations runbook, move the runner to another server before replacing the GitLab host.

## First implementation sequence

1. Create the change record and collect the required secret/input inventory.
2. Point `code.naudecoreventures.com` and `registry.code.naudecoreventures.com` to the server IPv4 address.
3. Install Ubuntu 24.04 LTS with software RAID 1.
4. Apply the SSH, firewall, patching, RAID, and SMART baseline.
5. Install GitLab EE without a paid license; it operates with Free features.
6. Configure TLS, sign-up restrictions, SMTP, Container Registry, backups, and 2FA.
7. Create the NCV group structure and access model.
8. Install one constrained Linux Docker runner.
9. Connect GitLab Self-Managed to Jira Cloud.
10. Create CI templates and one pilot project.
11. Migrate one non-critical Azure DevOps repository and its pipeline.
12. Validate test, package, experimental, beta, stable, rollback, and release-note flows.
13. Migrate remaining repositories in controlled waves.
14. Add a separate Windows runner and later a macOS runner.

## Non-negotiable rules

* Never configure the two NVMe drives as RAID 0.
* Never treat RAID 1 as a backup.
* Never put a permanent personal access token inside a customer application.
* Never rebuild a release merely to promote it from Experimental to Beta or Stable.
* Never run untrusted pipelines on the GitLab host runner.
* Never allow unrestricted privileged Docker jobs on the GitLab host.
* Never migrate plaintext Azure secrets into repository YAML.
* Never perform an Azure cutover without a final mirror verification and documented rollback point.
* Never deploy a desktop updater to customers before interrupted-download, signature, rollback, locked-file, antivirus, and restart tests pass.

## In this documentation

| Section | Contents |
| - | - |
| Platform overview | Server assessment, assumptions, and the platform decision |
| Governance | Accepted architecture decisions and the naming/branching convention |
| Integrations | Connecting AI tools to the NCV GitLab MCP server |
| Go-Live | Stage-gated acceptance checklists (Gates Aâ€“T) and the immediate no-go list |

Runbook sections (implementation, operations, developer workflow, migration, CI/CD, releases, security/DR) are ported from the numbered source documents in the `deployment` folder and land here section by section.

Source of record: `gitlab-platform/handbook` on `code.naudecoreventures.com` — changes merge to `main` and deploy automatically.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.