How graphicshack/travail_de_session_inf1007 works
This is a browser-based client and administrator portal for managing users and network decoders. Users sign in and view a decoder summary; administrators manage clients and their decoder assignments, then inspect decoder status or issue reset, reinitialization, shutdown, and channel changes. The graph separates page controllers, API services, decoder/user domain models, and the server/data layer. Source excerpts show frontend API calls and decoder-model behavior, but the server implementation and HTML wiring were not sampled, so those connections are limited or marked unverified.
Main entry points: decoderController.js Decoder controls · pages Portal pages · decoderService.js Decoder API service · clientController.js Client management
Components 20
Portal workflows
- Portal pages
pages - Authentication
js/controllers/authController.js - Client management
js/controllers/clientController.js - Dashboard
js/controllers/dashboardController.js - Decoder controls
js/controllers/decoderController.js
API services
- User API service
js/services/userService.js - Decoder API service
js/services/decoderService.js - API configuration
js/utils/config.js
Domain models
- User model
model/Utilisateur.js - Administrator model
model/Administrateur.js - Decoder model
model/Decodeur.js - Decoder states
model/EtatDecodeur.js - Decoder operations
model/Operation.js - Operation statuses
model/StatutOperation.js - Decoder content
model/Contenu.js
Server and data
- Express server
js/server.js - User records
data/users.json
Other components
- Portal user
- Local API
- Decoder endpoint
Connections 25
- Portal user → Portal pages: uses
- Portal pages → Authentication: hosts
- Portal pages → Client management: hosts
- Portal pages → Dashboard: hosts
- Portal pages → Decoder controls: hosts
- Authentication → User API service: authenticates
js/controllers/authController.js - Client management → User API service: manages clients
js/controllers/clientController.js - Client management → Decoder controls: displays decoders
js/controllers/clientController.js - Dashboard → Decoder API service: requests status
js/controllers/dashboardController.js - Dashboard → Authentication: reads user
js/controllers/dashboardController.js - Decoder controls → Decoder API service: controls decoders
js/controllers/decoderController.js - Decoder controls → Authentication: reads user
js/controllers/decoderController.js - Decoder controls → Client management: unassigns decoder
js/controllers/decoderController.js - User API service → API configuration: reads API URL
js/services/userService.js - Decoder API service → API configuration: reads endpoints
js/services/decoderService.js - User API service → Local API: requests user routes
js/services/userService.js - Decoder API service → Local API: requests channel routes
js/services/decoderService.js - Decoder API service → Decoder endpoint: sends actions
js/services/decoderService.js - Decoder controls → Decoder model: updates state
js/controllers/decoderController.js - Decoder model → Decoder states: uses states
model/Decodeur.js - Decoder model → Decoder operations: records operations
model/Decodeur.js - Decoder operations → Operation statuses: uses statuses
model/Operation.js - Administrator model → User model: extends user
model/Administrateur.js - Local API → Express server: served by
- Express server → User records: may persist users