How walllu/marketdays works
MarketDays is a Django trading application for local, time-bounded markets: users join a session, list items, propose or respond to exchanges, and ultimately exchange items in person. The central runtime path is browser request → URL routing → views, which coordinate forms and persistent domain records and render pages. Profiles, session participation, item ownership, offers, and offer contents are distinct domain stages. The README also describes authentication and market-location exchange. Source excerpts are partial, so unshown feature-specific connections are omitted.
Main entry points: views.py Request handlers · urls.py Project routing · forms.py Profile and item forms · models.py Tradeable items
Components 14
Web entry and pages
- Project routing
MarketDays/urls.py - Market routing
market/urls.py - Request handlers
market/views.py - Market pages
templates/market
Trading domain
- Tradeable items
market/models.py - Trade offers
market/models.py - Offer item sides
market/models.py
Accounts and sessions
- Account pages
templates/registration - Profile and item forms
market/forms.py - User profiles
market/models.py - Market sessions
market/models.py - Registration package
Persistent state
- Relational database
Other components
- Market user
Connections 21
- Market user → Project routing: requests pages
MarketDays/urls.py - Project routing → Market routing: includes routes
MarketDays/urls.py - Project routing → Request handlers: routes requests
MarketDays/urls.py - Market routing → Request handlers: routes requests
market/urls.py - Request handlers → Profile and item forms: uses forms
market/views.py - Request handlers → User profiles: reads and writes
market/views.py - Request handlers → Market sessions: reads and writes
market/views.py - Request handlers → Tradeable items: reads and writes
market/views.py - Request handlers → Trade offers: reads and writes
market/views.py - Request handlers → Offer item sides: creates trade sides
market/views.py - Request handlers → Market pages: renders pages
market/views.py - Profile and item forms → User profiles: validates profile
market/forms.py - Profile and item forms → Tradeable items: validates item
market/forms.py - User profiles → Relational database: persists records
market/models.py - Market sessions → Relational database: persists records
market/models.py - Tradeable items → Relational database: persists records
market/models.py - Trade offers → Relational database: persists records
market/models.py - Offer item sides → Relational database: persists records
market/models.py - Project routing → Registration package: includes registration
MarketDays/urls.py - Market user → Account pages: registers or logs in
README.md - Market user → Relational database: exchanges in person
README.md