Frequently asked questions

No. Despite the name, Conduit's package.json has no dependency on Redux or React Redux. "Redux" here reads as a second iteration of an earlier "Conduit" project, not a reference to the state-management library.

No. Receipt scanning (NEXT_SCAN_SERVICE_URL, SCAN_JWT_PRIVATE_KEY) is a separate, optional service. Without it, the MANUAL tab on the report form still works — you pick a merchant, a date, and add components with quantity and price by hand. See Environment Variables.

It's the access key encoded in the QR code on a Brazilian electronic consumer receipt (Nota Fiscal de Consumidor Eletrônica) — a 44-digit number. Conduit's scan form accepts it either via camera or typed in directly, labeled NFC-e_CODE in the UI.

Yes. A Member can belong to multiple squads through SquadCrew, but has exactly one activeSquadId at a time — the squad whose missions and item history you're currently viewing. Conduit also won't let you leave or delete your only squad.

Bun. The repo ships a bun.lock, the Dockerfile is built on oven/bun:1, and the project's own contributor guidelines state it directly: "This project uses bun."

The internationalization framework (next-intl) is wired in, and the project's own guidelines require "every text" to go through the /messages translation files — but as of this writing, only messages/en.json exists in the repository. English is what ships today.

To whatever SENTRY_DSN points at, via the @sentry/nextjs SDK. The example configuration in .env.example points that DSN at a self-hosted GlitchTip instance — a Sentry-API-compatible, open-source error tracker — rather than Sentry's own hosted service.

Through the bundled multi-stage Dockerfile, written with Coolify's build-argument injection in mind. On start, the container runs bun run prisma migrate deploy before bun run start, so migrations apply automatically on every deploy. See Deploying with Docker.