Leadgener from an empty repository: 45 hours to a dev environment

Leadgener finds and tracks business opportunities in public sources. It started from an empty repository on 8 October 2026; it is still being built and runs only in a dev environment. A new product cannot be judged until it runs deployed, behind its own sign-in.

Copy the reference, change the palette

Leadgener's ADR-02, accepted on the first day, makes Reputo, our reference product, the source of truth for technology, patterns and components. Only the colour palette changes; any other deviation needs its own ADR.

The first commit held only product documents. Ten seconds later came the toolkit, vendored unchanged: 167 files, 11,414 lines. Twelve minutes in, the backend skeleton followed on Reputo's patterns, with tenancy, onboarding and organizations and without billing.

The next six hours went into Leadgener's domain: capturing notices from public sources, documents and a keyword dictionary, an evidence-based assessment with a selectable model provider, and screens to review the results. At hour 23 came the deploy, ported from Reputo: CI file, Dockerfiles, Compose file and deploy scripts.

Where the 45 hours went

• Hour 30: the GitLab project was created; by choice, the repository stayed local until then.
• Hour 31: on main the tests passed, then dotnet restore in the image build hung: NU1301 after ten minutes, still retrying half an hour later. Reputo had hit the same hang on 2 October and fixed it with docker build --network host: the Docker-in-Docker bridge has a larger MTU than the runner's network. The port had dropped the flag. One merge request restored it, and the images were built nine minutes after it merged.
• Hour 45: deploy:dev is a manual job, and it waited 13.5 hours overnight. Then, in 1 minute 50 seconds, it started seven containers, created the Keycloak realm and passed a health gate of six checks: API, app, realm, login theme and two landing pages.

For a team starting a product on the toolkit, Leadgener's record is about two days to a deployed dev environment, and the work in them went mostly into the product. Later that day, Leadgener replaced its vendored toolkit with the NuGet packages, pinned to one version. The CI file and deploy scripts remained ported, and Leadgener's first pipeline shows the cost: the reference's CI file carried the flag with a comment explaining it, and the port dropped both. Diff your pipeline against the reference's before your first push to main.