Platform overview and recommendation
Target URL:https://code.naudecoreventures.com · Prepared: 2026-08-11
Purpose: production implementation, operations, developer onboarding, Azure DevOps migration, CI/CD, package/release management, and desktop update-channel design.
Final recommendation
Use a single-node GitLab Self-Managed EE installation running with the Free feature set on Ubuntu 24.04 LTS, installed from GitLab’s official Linux package. The initial server will host:- Private Git repositories.
- GitLab CI/CD control plane.
- GitLab Package Registry, including Generic Packages for arbitrary release files such as EXE, ZIP, AppImage, DEB, and RPM artifacts. DEB/RPM files are downloadable artifacts here; this design does not claim native apt/yum repository semantics.
- GitLab Container Registry.
- GitLab Releases and release notes.
- Jira integration.
- One tightly limited Linux Docker runner for low-volume CI.
- The release-index repositories that expose
experimental,beta, andstablechannel manifests.
- Windows runner: required for native Flutter Windows builds, EXE/MSIX/Inno packaging, and Windows signing.
- macOS runner: required for iOS/macOS builds, Xcode signing, TestFlight, and App Store Connect.
- Two offsite backup repositories: application data and configuration/decryption secrets are encrypted separately because RAID 1 is not a backup.
Server assessment
The server is intentionally configured as GitLab first, runner second. Its 64 GB RAM and mirrored NVMe storage are strong for this role, but the CPU is the constraint. The co-located runner starts with
concurrent = 1, a two-CPU limit, and an 8 GB memory limit. Treat the first month as 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 inexpensive server before replacing the GitLab host.
Assumptions used in this documentation
- “Azure” means Azure DevOps Services, specifically Azure Repos, Azure Pipelines, Azure Artifacts, variable groups, secure files, and service connections.
- Jira Cloud remains the work-management source of truth; Azure Boards are not migrated into GitLab.
- The source repositories are private.
- Release-only GitLab projects may be public or may enable anonymous package pulls so installed customer applications do not contain a permanent GitLab credential.
- No production secret, code-signing key, Apple credential, server IP address, SMTP credential, or Azure token is stored in this documentation. Each runbook defines where credentials must be inserted without inventing values.
- The initial scale is a small engineering team and approximately three build requests per hour, not three simultaneous heavy builds.