How jambtc/yii2-fidelity.dashboard works
Fidelize Dashboard is a Yii2 web application for managing loyalty programs, merchants, stores, point-of-sale activity, and blockchain configuration. The main user workflow is account registration or sign-in, followed by dashboard and administrative operations on those records; controllers handle requests and ActiveRecord models represent persisted data. The tree also shows invoices, subscriptions, notifications, API keys, and rules-engine requests. Relationships below are limited to README statements, excerpts, and SOURCE INDEX references; several controller and integration details were not sampled.
Main entry points: SiteController.php Site and access · BackendController.php Admin dashboard · Stores.php Stores · Nodes.php Blockchain nodes
Components 22
Accounts and dashboard
- Site and access
controllers/SiteController.php - User accounts
models/Users.php - Registration
models/SignupForm.php - Admin dashboard
controllers/BackendController.php
Loyalty operations
- Merchants
models/Merchants.php - Stores
models/Stores.php - Point of sale
models/Pos.php - Invoices
models/Invoices.php - Subscriptions
controllers/SubscriptionsController.php - API keys
models/Apikeys.php
Blockchain settings
- Blockchains
models/Blockchains.php - Blockchain nodes
models/Nodes.php - Host settings
models/Host.php - Owner settings
models/Owner.php - Web app utilities
components/WebApp.php
Messaging and rules
- Rules engines
models/RulesEngines.php - Engine requests
controllers/RulesenginerequestsController.php - Notifications
models/Notifications.php - Notification readers
models/NotificationsReaders.php - Logs
models/Logs.php
Other components
- Dashboard user
- Application database
Connections 26
- Dashboard user → Site and access: uses
- Dashboard user → Admin dashboard: manages
- Site and access → Registration: registers with
controllers/SiteController.php - Site and access → User accounts: authenticates
controllers/SiteController.php - Site and access → Invoices: loads
controllers/SiteController.php - Admin dashboard → Notifications: uses
controllers/BackendController.php - Admin dashboard → Notification readers: uses
controllers/BackendController.php - Admin dashboard → Web app utilities: uses
controllers/BackendController.php - Registration → User accounts: creates
models/SignupForm.php - Stores → Merchants: references
models/Stores.php - Stores → Blockchains: references
models/Stores.php - Blockchain nodes → Blockchains: references
models/Nodes.php - Web app utilities → Blockchain nodes: uses
components/WebApp.php - Rules engines → Web app utilities: encrypts with
models/RulesEngines.php - Engine requests → Rules engines: searches
controllers/RulesenginerequestsController.php - Notifications → Notification readers: references
models/Notifications.php - User accounts → Application database: persists via
models/Users.php - Merchants → Application database: persists via
models/Merchants.php - Stores → Application database: persists via
models/Stores.php - Point of sale → Application database: persists via
models/Pos.php - Invoices → Application database: persists via
models/Invoices.php - Blockchains → Application database: persists via
models/Blockchains.php - Blockchain nodes → Application database: persists via
models/Nodes.php - Rules engines → Application database: persists via
models/RulesEngines.php - Notifications → Application database: persists via
models/Notifications.php - Logs → Application database: persists via
models/Logs.php