How ripwords/timesheet works
Project type and purpose
• This is a full-stack timesheet application organized as a monorepo.
• It comprises three main “apps”:
• A web dashboard (apps/dashboard) built with Nuxt 3 + Vue.
• A desktop client (apps/desktop) built with Nuxt + Tauri.
• A backend API server (apps/server) running on Bun + Drizzle ORM.
• The root also contains Docker/Docker-Compose configurations to spin up the system in containers.
Main components
a. Frontends
– Web Dashboard (Nuxt/Vue)
– Desktop Client (Nuxt + Tauri)
b. Backend API
– Bun runtime
– Entry point index.ts
– Module boundaries: auth, admin (departments, users, financials, reports, settings), projects, time-entries, time-tracker, services (cron jobs), middleware
c. Database
– PostgreSQL (drizzle.config.ts + drizzle migration/seed files)
d. External services
– SMTP/mail provider (apps/server/utils/mail.ts)
– Possible third-party auth/email (e.g., via Eden plugin)
e. Infrastructure
– Docker containers (web, desktop, api, database) orchestrated by docker-compose
– Entrypoint shell scripts (apps/server/entrypoint.sh)
Relationships and data flows
• Both frontends (web & desktop) → communicate via HTTPS to the Backend API.
• Backend → reads/writes to the PostgreSQL database via Drizzle ORM.
• Backend Cron Services → run recurring jobs (budget calculations, timer notifications) on schedule → update DB or send emails.
• Backend Mail Utility → sends outgoing emails to SMTP provider.
• Docker-Compose → brings up all above containers and sets network links.
Architectural patterns and design principles
• Monorepo with clear separation of concerns: each app in its own directory.
• Modular backend: domain folders under src (auth, admin, projects, etc.).
• Use of middleware for global auth guard.
• Declarative DB migrations/seeds (Drizzle).
• Desktop client uses Tauri’s secure Rust bridge for native capabilities.
• Frontends share composables, plugins, layouts, pages (Nuxt conventions).
Essential elements to capture
• All three “apps” and how they deploy/run (containers or Tauri bundle).
• API endpoints/modules and middleware flow.
• DB migrations and seeds as part of the backend startup.
• Cron jobs as background services within the backend.
• Interactions with external SMTP/email service.
• Docker-Compose orchestration of containers.