The problems we solve
-
Tests that only run on developers' machines.
-
Pipelines configured by hand, not versioned, that nobody dares to touch.
-
An image rebuilt for each environment: what goes to production is not what was tested.
-
Production secrets stored in the CI tool.
-
No visibility into the dependencies you ship.
What we put in place
-
Thin pipelines driven by moon, runnable locally.
-
A quality gate enforced before every merge.
-
One image per commit, deployed by digest to every environment.
-
A deployment started from inside the isolated environments.
-
Static analysis, SBOM and pinned versions of the toolchain.
-
A documented and reversible choice of code forge.
Articles
Production secrets: take them out of the forge with Dokploy
The Git forge is read by more people than production. With Dokploy, each environment holds its own secrets: the CI never sees them and holds no Dokploy key.
11 min read
Build once, promote many: deploying by digest with Dokploy
One image per commit, built and scanned once, promoted by digest: a job placed inside each isolated environment calls the API of its own Dokploy instance.
11 min read
CI supply chain: pin your tools and produce an SBOM
Actions pinned by commit SHA, images by digest, tools by checksum, dependencies through a proxy: secure the CI and ship every image signed, with its SBOM.
11 min read
Thin CI pipelines driven by moon in a monorepo
In a monorepo, moon decides what to test while the CI orchestrates: a thin YAML, the same tasks run locally and a sound comparison base, never HEAD~1.
11 min read
Symfony code quality with free tools: PHPStan, Rector, Deptrac
SonarQube Community Build does not analyse pull requests. PHPStan, PHP-CS-Fixer, Rector and Deptrac, run by moon, check them free of charge in a monorepo.
11 min read