How kev1nweng/myphlex works
Project type and purpose
• This is a full-stack, cross-platform password-generation solution (“秘符灵匣 Myphlex”), split into two submodules:
• myph – the server side (REST/HTTP API, business logic, storage)
• lex – the client side (web UI for configuration and password retrieval)
• Purpose: securely generate and serve user-specific passwords on demand, protected by a time-based dynamic passcode.
File structure
• Top level:
• .github/workflows – CI/CD pipelines (submodule_release.yml)
• .gitmodules – points to myph and lex
• README.md, LICENSE, .gitignore
• Submodules:
• myph – server implementation (API controllers, auth module, password-engine, persistence)
• lex – client implementation (HTML/CSS/JS or framework code, UI components, HTTP client)
README for additional insights
• Architecture implied: browser-based UI (lex) calls server endpoints (myph)
• Key flows: initial configuration → dynamic passcode rules + static seed setup → subsequent password requests authenticated via dynamic code → server returns generated password
• Server must handle sessions (10-minute auto-logout), rule parsing, seed storage, password derivation.