Rebuild payment API with PocketBase and Go - #16
Merged
Conversation
Phloraxx
marked this pull request as ready for review
July 26, 2026 12:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the Fastify/SQLite prototype with the reviewed Go + PocketBase implementation and embedded React operator UI.
Key changes:
/app/pb_data/api/webhookcompatibility route gated behind explicit migration configValidation
Local release gate passed:
npm ci+npm audit --audit-level=highgofmt+git diff --checkgo test -count=1 ./...go test -race -count=1 ./internal/...go vet ./...GitHub Actions CI run #45 also passed every step, including the production Docker build, for head
9a065bf9eb0e6446640af2b3cb57902d2defbd10.Production cutover blocker
Do not merge/deploy yet. Dokploy's persistent volume is already saved, but production still needs new strong
PAYGATE_API_KEYandSMS_WEBHOOK_SECRETvalues before the new server can pass startup validation. The old one-characterWEBHOOK_SECRETis retained only for the explicitly enabled temporary legacy relay route during migration.