How skywors/tempora works
Project type and purpose
• This is a monolithic full-stack PHP web application (“Tempora”) following an MVC-style organization.
• It provides user account management (register, login, password reset), a dashboard UI, and a small JSON-based API endpoint for user data.
File structure
• public/ holds all static assets (images, CSS, JS) and the single entry point (index.php) for the web server.
• src/ contains the PHP application logic, subdivided into:
• Configs (routing configuration in routes.json)
• Controllers (web UI controllers under Accounts, Dashboard, Error, plus an API subtree)
• Models (Database connection, Entities, Repositories, Services)
• Utils & Factories (helper classes: routing, navbar, element building)
• Router.php (front-controller dispatch)
• views/ (template components and layouts)
• sql/database.sql defines the relational schema.
• composer.json/lock declares PHP dependencies; phpunit.xml and tests/ enable automated testing of the API and error flows.
• logs/ captures runtime logs.
README
• It shows minimal Apache2/Nginx VirtualHost configurations, confirming that all dynamic routing is funneled through public/index.php.
• No additional microservices or external data stores are mentioned besides a mail service for email notifications.
• Web server (green),
• PHP application layers (blue),
• Database (orange),
• External services (purple),
• Static assets (gray).
• Edge cases like error handling (ErrorController) and logging.
Detailed capture of essential components
• Don’t forget minor but important pieces: RouterFactory, NavbarFactory, Utils (Cookie, Lang, System), and the PHPUnit test harness.
• How public/scripts (engine.js, toolbar.js, theme.js) and public/styles feed into the client-side UI.