How pglombardo/passwordpusher works
Main Components
a. Frontend Layer:
• Web Interface (Rails Views + Assets)
• JavaScript Controllers (Stimulus.js)
• Theme System
• Internationalization System
b. Application Layer:
• Rails Controllers
• Authentication System (Devise)
• Admin Dashboard
• Background Jobs System
c. Data Layer:
• Database (supports MySQL, PostgreSQL, MariaDB)
• Active Storage for file handling
• Encrypted Storage System
d. External Services:
• Email Service
• Translation Service
• Analytics (optional)
Key Architectural Patterns to Highlight
a. MVC Architecture:
• Models: Password, FilePush, URL, User, View
• Controllers: Separate controllers for each resource
• Views: ERB templates with layout system
b. Service-Oriented Components:
• Authentication Service
• Encryption Service
• Background Job Processing
• Internationalization Service
[User/Browser Layer]
• ▼
[Load Balancer/Reverse Proxy]
• ▼
[Web Application Layer]
• Frontend Components
• Asset Pipeline
• JavaScript Controllers
• View Templates
• Application Core
• Controllers
• Models
• Services
• Background Jobs
• Security Layer
• Authentication
• Authorization
• Encryption
• ▼
[Data Layer]
• Primary Database
• Active Storage
• Cache Store
Important Flows to Highlight
a. Password Push Flow:
User → Web Interface → Controller → Encryption Service → Database
b. Password Retrieval Flow:
User → Web Interface → Controller → Authentication → Decryption → View
c. Background Jobs Flow:
Scheduler → Job Queue → Worker → Database Cleanup
Key Technical Details
• Encryption system using lockbox
• Multi-language support (29 languages)
• Theme system with 26 themes
• Docker/Kubernetes deployment options
• Background job processing
• API endpoints for programmatic access