SXCHNGE's local stack previously started without a Sendico identity or API connection. Add an optional local Compose overlay and server-side session worker, keeping the adapter's HTTPS defaults and loopback HTTP exception intact. The worker uses a scoped Vault AppRole, renews the public API session every 20 minutes, and atomically supplies BFF's read-only token file.
The configured stands are running: SXCHNGE at https://localhost:5126, Sendico Product at http://localhost:3000, and Backoffice at http://localhost:4000. A dedicated local integration organization/account/client was provisioned without seeding funds or payment destinations. No Sendico source changes are included.
Validation: make build, make up, make test-dev-tooling, make test-dev-infra, make test-dev, and git diff --check passed. Both UIs and API health endpoints returned 200; all checked containers are healthy. Authenticated currency/ledger reads and forced same-account token renewal passed. No email or payment was sent. The pre-existing notification sender edit is excluded.
Closes#52. Stacked on #51; merge identity prerequisites and #51 first, with Sendico #2897 deployed before integration use. Setup, credentials, recovery, operator UX review and validation are documented in docs/local-sendico.md. Browser trust for the exported Caddy CA remains an operator action; no system trust settings are changed.
SXCHNGE's local stack previously started without a Sendico identity or API connection. Add an optional local Compose overlay and server-side session worker, keeping the adapter's HTTPS defaults and loopback HTTP exception intact. The worker uses a scoped Vault AppRole, renews the public API session every 20 minutes, and atomically supplies BFF's read-only token file.
The configured stands are running: SXCHNGE at https://localhost:5126, Sendico Product at http://localhost:3000, and Backoffice at http://localhost:4000. A dedicated local integration organization/account/client was provisioned without seeding funds or payment destinations. No Sendico source changes are included.
Validation: make build, make up, make test-dev-tooling, make test-dev-infra, make test-dev, and git diff --check passed. Both UIs and API health endpoints returned 200; all checked containers are healthy. Authenticated currency/ledger reads and forced same-account token renewal passed. No email or payment was sent. The pre-existing notification sender edit is excluded.
Closes #52. Stacked on #51; merge identity prerequisites and #51 first, with Sendico #2897 deployed before integration use. Setup, credentials, recovery, operator UX review and validation are documented in docs/local-sendico.md. Browser trust for the exported Caddy CA remains an operator action; no system trust settings are changed.
tech
added the backend label 2026-10-16 08:20:14 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
SXCHNGE's local stack previously started without a Sendico identity or API connection. Add an optional local Compose overlay and server-side session worker, keeping the adapter's HTTPS defaults and loopback HTTP exception intact. The worker uses a scoped Vault AppRole, renews the public API session every 20 minutes, and atomically supplies BFF's read-only token file.
The configured stands are running: SXCHNGE at https://localhost:5126, Sendico Product at http://localhost:3000, and Backoffice at http://localhost:4000. A dedicated local integration organization/account/client was provisioned without seeding funds or payment destinations. No Sendico source changes are included.
Validation: make build, make up, make test-dev-tooling, make test-dev-infra, make test-dev, and git diff --check passed. Both UIs and API health endpoints returned 200; all checked containers are healthy. Authenticated currency/ledger reads and forced same-account token renewal passed. No email or payment was sent. The pre-existing notification sender edit is excluded.
Closes #52. Stacked on #51; merge identity prerequisites and #51 first, with Sendico #2897 deployed before integration use. Setup, credentials, recovery, operator UX review and validation are documented in docs/local-sendico.md. Browser trust for the exported Caddy CA remains an operator action; no system trust settings are changed.