Release engineering

Build once. Prove it in staging. Promote the same artifact.

IntelliconOps is delivered through a governed CI/CD pipeline that tests every pull request, builds immutable container images addressed by commit SHA, validates them in an isolated staging environment, and promotes the exact same image digests to production.

Watch the pipeline walkthrough Book a demonstration

Pipeline stages

Pull request
A feature branch opens a pull request; CI runs PHP, frontend, Python and secret-scan checks.
Build once
The trusted runner builds immutable images and publishes them by commit SHA to GHCR.
Staging
An isolated Compose stack pulls the digests and runs smoke tests.
Approval
The production environment requires an explicit approval.
Production
The same digests deploy to the Droplet and pass a public HTTPS check.

The delivery model

A straight line from developer change to verified production release.

One immutable artifact travels through the pipeline; it is never rebuilt on the way to production.

Pull request to production

Every step gates the next one.

Select any screenshot to inspect it at full size.

1

Three isolated environments

Development stays local and unchanged on port 8101. Staging runs as its own Compose project in WSL. Production runs on a hardened DigitalOcean Droplet. Each keeps separate data and identity.

2

Feature branch and pull request

Every change arrives on a feature branch and opens a pull request against protected main, keeping the developer stack untouched.

3

Checks on the pull request

GitHub-hosted CI runs PHP quality and tests, a frontend build, Python tests, Compose validation and a committed-secret scan in parallel before merge.

4

Build once, tag by commit SHA

The trusted WSL runner builds immutable app, web and worker images, publishes them to GitHub Container Registry and records their digests in a release manifest.

5

Isolated staging deployment

Staging pulls by digest into its own Compose project with separate volumes, never touching development data, credentials or the live stack.

6

Staging smoke and validation

Readiness checks confirm the release SHA, migrations are complete, services are healthy and a harmless mock job completes before production is eligible.

7

Promote the same digests

After approval, the exact image digests that passed staging deploy to production over SSH. Nothing is rebuilt on the Droplet.

8

Public HTTPS verification

The pipeline checks the public readiness endpoint and release SHA, and automatically rolls back to the previous release if a health check fails.

Release identity

The same short SHA appears in every environment.

The release SHA is reported by the readiness endpoint and shown in the application footer, so staging and production always expose exactly what is running.

Staging footer

After smoke tests pass, staging shows the merged commit SHA that the isolated stack is running.

Production footer

The promoted digests carry the same SHA, verified against the public endpoint before the deployment is marked successful.

See it end to end

Watch one change travel from a pull request to production.

The CI/CD walkthrough video follows a real release through automated checks, immutable image builds, isolated staging and verified production promotion.

Watch on YouTube