How pjn2work/cdc works
CDC is a membership and community-commerce application: users manage members and dues, record donations and member purchases, and track sellers, expenses, and inventory. Its main workflow enters through authenticated web pages or REST endpoints, validates and authorizes requests, applies domain operations, and persists records in SQLite; web pages and API responses return results to the user. The tree and excerpts confirm the item API/CRUD and parts of member web handling, while several other routes and domain implementations are unsampled, so their internal links are kept broad. A payment dashboard is also present, but its runtime wiring is only partly evidenced.
Main entry points: web Web pages · main.py FastAPI application · api REST endpoints · members.py Member management
Components 21
Application entry
- FastAPI application
app/main.py - Web pages
app/web - REST endpoints
app/api
Access and security
- OAuth routes
app/sec/security.py - Token and scopes
app/sec/security.py
Business domains
- Member management
app/web/members.py - Dues payments
app/web/dues_payments.py - Member payment links
app/web/member_due_payment.py - Member donations
app/web/members.py - Items and categories
app/api/items.py - Member purchases
app/web/members_items.py - Seller purchases
app/web/sellers_items.py - Sellers and expenses
app/web/sellers.py - Other domain pages
app/web
Persistence and reporting
- Member operations
app/db/crud_member.py - Item operations
app/db/crud_items.py - Data schemas
app/db/schemas - Domain models
app/db/models - SQLite database
app/db/database.py - Payment dashboard
app/dash_app/callbacks.py
Other components
- Application user
Connections 25
- Application user → FastAPI application: sends requests
- FastAPI application → Web pages: dispatches pages
- FastAPI application → REST endpoints: dispatches API
- FastAPI application → OAuth routes: mounts routes
- Web pages → Token and scopes: checks web token
- REST endpoints → Token and scopes: checks API token
- OAuth routes → Token and scopes: issues tokens
- Web pages → Member management: routes member pages
- Web pages → Dues payments: routes dues pages
- Web pages → Member payment links: routes payment links
- Web pages → Member donations: routes donation pages
- Web pages → Member purchases: routes purchase pages
- Web pages → Seller purchases: routes purchase pages
- Web pages → Sellers and expenses: routes seller pages
- Web pages → Other domain pages: routes other pages
- REST endpoints → Items and categories: routes item API
- Member management → Member operations: calls operations
- Items and categories → Item operations: calls operations
- Member operations → SQLite database: queries and writes
- Item operations → SQLite database: queries and writes
- Payment dashboard → SQLite database: reads payments
- Item operations → Domain models: uses models
- Member operations → Domain models: uses models
- Items and categories → Data schemas: validates payloads
- Member management → Data schemas: validates forms