Install and verify Logmarq
Logmarq runs as one container with a web app and API. Use a release's exact image digest and matching instructions so you can identify what is installed and recover it later.
The website download path is prepared for future promoted releases. This guide announces no available version. A private candidate, a source change or a tag is not a supported release.
Get a promoted release
For a version that has actually been promoted and published, its files belong at
https://www.dekglas.com/downloads/logmarq/v<version>/. Replace the placeholder only with the
version supplied in a verified release record. The record provides release.json,
docker-compose.yml, LICENSE.md, SHA256SUMS.txt, reviewed release-notes.md and frozen documentation.
You do not need access to Dekglas's private source repository. There is no latest image tag.
Download the files into a new directory and run:
sha256sum -c SHA256SUMS.txt
Checksums detect a changed download; they do not independently authenticate a release. Verify the image signature with cosign 3 or newer, using the exact identity in its release record:
cosign verify "docker.io/dekglas/logmarq@sha256:<digest>" \
--certificate-identity "<identity-from-release-record>" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
Stop if the signature, digest, version or checksums disagree. A missing file or a failed verification is not permission to use a private candidate or skip verification.
Start on a Linux Docker host
The current image is built for Linux amd64. Use Docker Engine and Compose 2.24 or newer. Keep the data volume: it holds the default SQLite database and the key that seals saved integration credentials. A separate PostgreSQL deployment is optional and needs its own documented configuration and backup procedure.
Set LOGMARQ_IMAGE in .env to the exact image.ref from release.json, then:
docker compose pull
docker compose up -d
curl --fail http://localhost:8080/api/health
Expect status: ok. An unconfigured integration is different from an unhealthy application.
Open http://localhost:8080 and follow the quickstart.
The default port binds only to localhost. For remote access, put a TLS reverse proxy in front,
set LOGMARQ_PUBLIC_URL to the external HTTPS origin and set LOGMARQ_COOKIE_SECURE=true before
connecting GitHub. Host permissions, TLS, firewall rules and durable storage remain your
responsibility. Do not expose the container directly to the internet as a shortcut.
Before keeping the installation
- Record the version, digest and configuration choices without copying secrets into a report.
- Back up the database and credential-sealing key together and test recovery on an isolated copy.
- Restrict provider access to the repositories and operations you intend to use.
- Read security and privacy, upgrades and support and troubleshooting.