Files

Cauê Faleiros bd56170248 feat: let production select Mercado Pago and acknowledge simulated notifications

The production compose hard-coded the fake payment adapter; it now takes
PAYMENT_ADAPTER and the MP_* settings from the stack's environment, so the
sandbox can run with test credentials. A signed notification about a payment
Mercado Pago does not have, such as the panel's "Simular notificação", is
acknowledged instead of answering 500 and being retried; any other lookup
failure still raises.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-28 10:41:18 -03:00

__init__.py

first commit

2026-09-15 16:42:34 -03:00

Dockerfile.api

fix: harden week-two ordering, artwork and operations

2026-09-23 10:40:18 -03:00

Dockerfile.web

refactor: lay the repository out by role

2026-09-21 17:40:57 -03:00

nginx.conf.template

feat: give each Site product and the cart its own page

2026-09-24 16:56:58 -03:00

portainer.env.example

feat: let production select Mercado Pago and acknowledge simulated notifications

2026-09-28 10:41:18 -03:00

PRODUCTION_CHECKLIST.md

docs: move the engineering documents into docs/

2026-09-21 17:52:20 -03:00

production_preflight.py

fix: harden week-two ordering, artwork and operations

2026-09-23 10:40:18 -03:00

README.md

chore: remove the unused second stack definition

2026-09-21 13:48:22 -03:00

test_production_preflight.py

ci: publish images from every green push to main

2026-09-24 14:30:43 -03:00

README.md

Production deployment files

The DTF application is one Portainer-owned Docker Swarm stack. Gitea builds, tests, scans, and publishes the two application images, then calls the stack's Portainer webhook. Start with the short operator guide in ../PORTAINER.md.

The deployed stack is the repository's docker-compose.yml, not a file here.
Dockerfile.api and Dockerfile.web — prebuilt registry images.
portainer.env.example — non-secret Portainer variables.
production_preflight.py — fail-closed application/configuration validator.
PRODUCTION_CHECKLIST.md — production evidence checklist.

The current application remains deliberately blocked from production because real adapters and Docker-secret file loading are absent and current validation base images have unresolved HIGH/CRITICAL findings. No real provider or production service has been configured or contacted.