How dennislwm/archiveso works
Main Components
a) Frontend Layer:
• Lowdefy-based static frontend (hosted on Netlify)
• Auth0 authentication integration
• Components structure (requests, user avatar)
• Pages structure (home, login, profile, etc.)
b) Backend Layer:
• Python Flask server
• ArchiveBox integration
• HTTP Basic Authentication
• Docker containerization
c) External Services:
• Auth0 (OpenID Connect provider)
• MongoDB cluster
• Docker Hub (for image storage)
• Cloudflare Tunnel
• CircleCI (CI pipeline)
[Client Tier]
• ↓ ↑
[Application Tier]
• ↓ ↑
[External Services Tier]
Component Relationships
• User requests (→): Frontend to Backend
• Authentication flows (⇢): Frontend to Auth0
• Data persistence (↔): Backend to MongoDB
• CI/CD flows (⇢): Source to CircleCI to Docker Hub
• Deployment paths (→): Docker Hub to Production
Specific Implementation Details
• Frontend hosted on Netlify connecting to Auth0 for authentication
• Cloudflare Tunnel securing the connection to the Python Flask backend
• Docker container running the Flask application
• CircleCI pipeline flow for testing and deployment
• MongoDB integration for data persistence
Additional Elements
Important aspects:
• Load balancers where applicable
• Environment separation (development/production)
• Monitoring points
[Netlify Static Host] → [Lowdefy Frontend] ⇢ [Auth0]
• ↓
[Cloudflare Tunnel]
• ↓
[Docker Container: Flask Server] → [ArchiveBox]
• ↓
[MongoDB Cluster]
CI/CD Pipeline:
[GitHub] → [CircleCI] → [Docker Hub]