How noxify/turbo-lucia-starter works
Main Components
a) Frontend Layer (Next.js Application):
• Authentication Routes (/auth)
• Protected Dashboard Routes
• API Routes (for auth providers)
• Internationalization System
• Components Layer
b) Authentication Layer:
• Provider Connections (GitHub, Discord, Mock)
• Session Management
• User Management
c) Database Layer:
• PostgreSQL Database container with tables:
• Users
• OAuth Accounts
• Sessions
d) Package Ecosystem:
• UI Components (shadcn/ui based)
• Localization
• Database Access
• Helpers
• Logging
• Search Parameters
Relationships and Data Flow
• User authentication flow through providers
• API routes communication with auth layer
• Database interactions
• Package dependencies and usage
Specific Implementation Details
[External Auth Providers] <---> [Next.js API Routes]
• ↓
[Lucia Auth Layer] <---> [Database Layer]
• ↑
[Frontend Routes/Components]
• ↙ ↓ ↘
[UI] [Locales] [Helpers]
Key Technical Elements to Highlight
• Turborepo workspace structure
• Next.js 15.1 app router architecture
• Drizzle ORM integration
• Internationalization with next-intl
• Playwright test infrastructure
Development Tools Integration
• A section showing CI/CD workflow
• Testing infrastructure (Playwright)
• Tooling configuration flow
• Monorepo structure with clear package separation
• Authentication flow with multiple providers
• Database schema relationships
• Frontend routing and protection
• Shared package utilization
• Component grouping
• External service integration
• Clear separation of concerns
• Modular package structure
• Type-safe database access
• Secure authentication implementation
• Comprehensive testing capabilities
• Internationalization support
• Scalable UI component system