onesch

What an agent can do with the event-driven-payment-service corpus

onesch/event-driven-payment-service: Asynchronous payment processing service built with FastAPI, PostgreSQL, RabbitMQ, and SQLAlchemy, featuring the transactional outbox…

• Look up how event-driven-payment-service implements alembic, docker, event-driven, with answers cited to file and line.
• Reuse a worked example: the commit “initialize project structure and add payment model with Alembic…” (12 files · Python).
• Answer from event-driven-payment-service's real Python source instead of memory (Databases and storage engines).

• How does event-driven-payment-service implement alembic?
• What does alembic do in event-driven-payment-service?

Search the GitHub repository onesch/event-driven-payment-service with XERJ (https://hub.xerj.org/corpus/onesch--event-driven-payment-service).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/onesch/event-driven-payment-service event-driven-payment-service && git -C event-driven-payment-service checkout d4be973e951de720c5fdd83d7dcf2b4df34b0039
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./event-driven-payment-service --url http://127.0.0.1:9200 --prefix event-driven-payment-ser --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: MIT. Keep the copyright notice and credit the authors.

corpus onesch--event-driven-payment-service · Databases and storage engines
Related corpora: ann-benchmarks, act, parthacharyaaaaa/Tenjin, prsvt420/tyk
Case study: reference coding for agents