How ecotrust/tekdb works
Main Components
a. Frontend Layer:
• Explore Module (public-facing interface)
• Admin Interface (Django Admin)
• Login/Authentication System
• Static Assets (CSS, JS, images)
• GIS Interface Components
b. Backend Layer:
• Django Application Server
• Core Apps:
• TEKDB (main application)
• Accounts
• Lookup
• Relationships
• Configuration
• Explore
• Authentication/Authorization
c. Database Layer:
• PostgreSQL Database (with PostGIS extension)
• Data Models:
• Citations
• Places
• Media
• Resources
• Events
• Relationships
d. Infrastructure Components:
• Nginx Web Server (proxy)
• uWSGI Application Server
• Docker Containers
• Static/Media File Storage
Relationships and Data Flow
• HTTP requests from clients to Nginx
• Nginx proxy passes to uWSGI
• uWSGI communication with Django
• Django's interaction with PostgreSQL
• Static/Media file serving paths
• Authentication flow
• GIS data flow
Specific Implementation Details
[Client Browsers] → [Nginx Proxy] → [uWSGI] → [Django Apps] → [PostgreSQL]
• ↓
• [Static/Media Files]
b. Specialized components:
• GIS functionality (OpenLayers, PostGIS)
• Media handling system
• Authentication flow
• Configuration management
Additional Elements
• Notes about Docker containerization
• Development vs production environments
• Backup/restore paths
• Security boundaries
Key Integration Points
• Integration with external services
• API endpoints if any
• Where configuration affects the system
• Where custom middleware operates
GIS component interaction
Remember to include:
• Version information
• Environment variables
• Configuration paths
• Deployment considerations
• Backup/restore paths
• Security boundaries
• Scaling points
This will provide a comprehensive view of the system while maintaining clarity and usefulness for the development team.