Logmarq documentation

What Logmarq records, what it never does, and the objects you will work with.

Run Logmarq, connect GitHub, add a project, and record its releases with drafted notes.

Select an actually promoted release, verify its image and files, and start one container on a private local port.

Back up before changing versions, use release-specific recovery instructions, and understand the supported-release boundary.

Understand authentication, stored release data, provider access and outbound requests before operating Logmarq.

Separate startup, authentication, provider and record problems while preserving data and collecting a small safe report.

What a release record pins, where versions come from, and how new versions record themselves.

Internal notes drafted from the changes, customer notes as a checked subset, and where they go.

Which release each environment runs, who reported it, and how fresh the answer is.

Keep supporting an older version after a newer one ships, and see what each line needs.

The components inside each release, kept with the release, compared between releases, and exported.

Which customers run which release, answered without showing one customer to another.

Every term Logmarq uses in the app and these docs, A to Z, with a link to where it matters.