Run local SXCHNGE against the local Sendico stand with a provisioned server-side identity and verify both application endpoints.
Approach
Restore the existing Sendico dependency chain, configure the SXCHNGE local runtime and credential delivery, and document reproducible startup and connection checks. Preserve the public HTTP adapter and keep secrets out of source and Flutter.
Acceptance criteria
Both local product UIs and APIs respond successfully.
SXCHNGE uses the local Sendico public API with a valid integration identity.
Local configuration and credential provisioning are reproducible and documented.
Configuration checks pass and no secret values are committed.
Notes
Delivered in PR #53, branch local-stand-52, commit a5689876ff. Based on payments-50 / PR #51; Sendico runs payments-2896 / PR #2897. Merge prerequisites before this stacked PR. Nothing merged.
Both stacks are running. SXCHNGE https://localhost:5126; Sendico Product http://localhost:3000; Backoffice http://localhost:4000. All checked containers healthy, both UI/API endpoints HTTP 200, authenticated currency/ledger reads and forced same-account token renewal passed. make build, make up, make test-dev-tooling, make test-dev-infra, make test-dev and git diff --check passed.
The optional local worker uses a five-minute scoped Vault token and public API login every 20 minutes. Credentials remain in kv/services/bff/sendico; temporary operator input removed. No product transport validation changed, no Sendico tracked source changed, no email or funded payment executed. Existing notification sender edit preserved and excluded. Dedicated customer ledgers/destinations remain financial provisioning; the integration organization has no seeded funds. Browser CA trust is not modified automatically.
Durable setup, limits, recovery, UX/measurement review and validation: docs/local-sendico.md.
### Goal
Run local SXCHNGE against the local Sendico stand with a provisioned server-side identity and verify both application endpoints.
### Approach
Restore the existing Sendico dependency chain, configure the SXCHNGE local runtime and credential delivery, and document reproducible startup and connection checks. Preserve the public HTTP adapter and keep secrets out of source and Flutter.
### Acceptance criteria
- [x] Both local product UIs and APIs respond successfully.
- [x] SXCHNGE uses the local Sendico public API with a valid integration identity.
- [x] Local configuration and credential provisioning are reproducible and documented.
- [x] Configuration checks pass and no secret values are committed.
### Notes
Delivered in PR https://git.sendico.io/tech/sxchnge/pulls/53, branch local-stand-52, commit a5689876ff79a17b416074d20731f5827b946422. Based on payments-50 / PR #51; Sendico runs payments-2896 / PR #2897. Merge prerequisites before this stacked PR. Nothing merged.
Both stacks are running. SXCHNGE https://localhost:5126; Sendico Product http://localhost:3000; Backoffice http://localhost:4000. All checked containers healthy, both UI/API endpoints HTTP 200, authenticated currency/ledger reads and forced same-account token renewal passed. make build, make up, make test-dev-tooling, make test-dev-infra, make test-dev and git diff --check passed.
The optional local worker uses a five-minute scoped Vault token and public API login every 20 minutes. Credentials remain in kv/services/bff/sendico; temporary operator input removed. No product transport validation changed, no Sendico tracked source changed, no email or funded payment executed. Existing notification sender edit preserved and excluded. Dedicated customer ledgers/destinations remain financial provisioning; the integration organization has no seeded funds. Browser CA trust is not modified automatically.
Durable setup, limits, recovery, UX/measurement review and validation: docs/local-sendico.md.
tech
added the backend label 2026-10-16 08:02:58 +00:00
tech
self-assigned this 2026-10-16 08:02:58 +00:00
tech
added this to the SXCHNGE project 2026-10-16 08:02:58 +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.
Goal
Run local SXCHNGE against the local Sendico stand with a provisioned server-side identity and verify both application endpoints.
Approach
Restore the existing Sendico dependency chain, configure the SXCHNGE local runtime and credential delivery, and document reproducible startup and connection checks. Preserve the public HTTP adapter and keep secrets out of source and Flutter.
Acceptance criteria
Notes
Delivered in PR #53, branch local-stand-52, commit
a5689876ff. Based on payments-50 / PR #51; Sendico runs payments-2896 / PR #2897. Merge prerequisites before this stacked PR. Nothing merged.Both stacks are running. SXCHNGE https://localhost:5126; Sendico Product http://localhost:3000; Backoffice http://localhost:4000. All checked containers healthy, both UI/API endpoints HTTP 200, authenticated currency/ledger reads and forced same-account token renewal passed. make build, make up, make test-dev-tooling, make test-dev-infra, make test-dev and git diff --check passed.
The optional local worker uses a five-minute scoped Vault token and public API login every 20 minutes. Credentials remain in kv/services/bff/sendico; temporary operator input removed. No product transport validation changed, no Sendico tracked source changed, no email or funded payment executed. Existing notification sender edit preserved and excluded. Dedicated customer ledgers/destinations remain financial provisioning; the integration organization has no seeded funds. Browser CA trust is not modified automatically.
Durable setup, limits, recovery, UX/measurement review and validation: docs/local-sendico.md.
tech referenced this issue2026-10-16 09:27:19 +00:00