How seanmorley15/adventurelog works
Project type and purpose
• AdventureLog is a full-stack, open-source travel companion web application.
• Frontend: SvelteKit SPA with TailwindCSS and DaisyUI, uses Svelte MapLibre for maps.
• Backend: Django monolith (Django REST Framework, AllAuth, PostGIS) serving a REST API and server-rendered templates.
• Auxiliary “cdn” service to serve static assets and cache.
File structure
• Top-level directories:
• frontend/ – SvelteKit code, routes, components, build config, Dockerfile.
• backend/ – Django project, apps (adventures, achievements, integrations, users, worldtravel), Dockerfile, Nginx config, entrypoint.
• cdn/ – Python microservice (simple HTTP server + Nginx) for static files, Dockerfile.
• documentation/, brand/, .github/, tooling (docker-compose, Traefik kustomization).
• Deployment files: docker-compose.yml, docker-compose-traefik.yaml, kustomization.yml, GitHub Actions workflows for CI/CD.
• Configuration: .env.example files for frontend and backend; supervisord for process management; build scripts.
README
• Tech stack calls out SvelteKit, TailwindCSS, DaisyUI on client; Django + DRF + PostGIS + AllAuth on server.
• Features: logging adventures, map view, itineraries, sharing, world travel book.
Components
a. Client tier
• Web browser / mobile web → SvelteKit SPA
• Optional: Service Worker for offline caching
b. CDN tier
• Static assets (CSS, JS bundles, images, fonts) served by cdn/ service (Nginx + Python)
c. API & Web tier
• Traefik (or Docker-Compose reverse proxy) routes requests:
– /api/* → Django REST API (Gunicorn)
– /static/* → CDN service
– /* → SvelteKit SSR (via adapter in frontend) or direct SPA assets
• Nginx (inside backend container) fronts Gunicorn processes
• Django apps (adventures, users, integrations, worldtravel, achievements)
d. Data tier
• PostgreSQL with PostGIS extension (persistent data store)
• (Optional) Redis or in-memory cache if used for sessions / rate-limiting
e. External services
• OAuth providers via AllAuth (GitHub, OIDC, etc.)
• Email/SMS service for verification and notifications
• Tile provider (if MapLibre requires external tiles)
• Immich integration (optional photo storage)
Relationships & data flow
• User interacts with SvelteKit UI → HTTP(S) calls → Traefik → backend API → Django views/serializers → ORM queries Postgres → response → UI updates.
• Static asset fetches go → Traefik → CDN service → browser cache.
• Social login flows: backend ↔ external OAuth endpoint → callback to AllAuth in Django.
• Tiles: client direct to tile server or proxied through backend.
Architectural patterns & principles
• Monolithic service broken into Django “apps” (modular MVC pattern).
• Clear frontend-backend separation via REST API.
• Infrastructure as code with Docker Compose + Traefik + Kubernetes kustomization.
• CI/CD pipelines in GitHub Actions for each component.