1f6217d347
Portal: - Replace is_admin boolean with role column (admin/advanced/standard) - Settings UI: 3-tier portal role select + per-app role dropdowns - /portal-return endpoint: re-establishes session from JWT for sub-app back-links - /api/internal/nv-users: internal endpoint for NetworkView user sync - portal/migrate_roles.py: one-time DB migration script - Role badges (admin/advanced/standard) in topbar and settings table DigiServer: - Add editor and viewer roles (portal advanced->editor, standard->viewer) - PlaylistPermission model: grant viewer users edit access to specific playlists - app/utils/access.py: shared editor_required, admin_required, can_edit_playlist helpers - Content routes: editor_required on create/delete, per-playlist permission check on mutations - Admin: playlist_permissions route + template to manage viewer playlist grants - Base template: hide Admin nav for viewers, Portal button (⬡) returns to portal - content_list_new: hide create/delete for viewers; Manage vs View button per permission - manage_playlist_content: view-only mode when user lacks edit permission NetworkView: - backend/src/middleware/rbac.js: requireRole + requireWriteAccess helpers - site_permissions table: one site per advanced user - All mutating routes guarded (admin=all, advanced=assigned site, viewer=read-only) - Portal SSO auto-upsert: user row synced from X-Auth-Role on every request - GET /api/users: merges portal users list with local NV data (all 4 portal users visible) - GET/PUT /api/users/:id/site-permission: assign site to advanced user - Settings Users tab: role badges, site dropdown for advanced, (portal only) indicator - Sidebar: ⬡ Portal button between Settings and Logout - Frontend build: VITE_API_BASE=/networkview/api now set in start-dev.sh IT Assets / Server Monitor: - portal_sso.py updated: map advanced->editor/viewer, standard->readonly - AdminUser model: add editor role + is_editor property
Server Monitoring System v2 - Enhanced Architecture
New Project Structure
Server_Monitorizare_v2/
├── app/
│ ├── __init__.py # Flask app factory
│ ├── models/ # Database models
│ │ ├── __init__.py
│ │ ├── device.py # Device model
│ │ ├── log.py # Log model with message aliases
│ │ └── file.py # File uploads model
│ ├── api/ # REST API endpoints
│ │ ├── __init__.py
│ │ ├── logs.py # Log endpoints
│ │ ├── devices.py # Device management
│ │ ├── files.py # File upload handling
│ │ └── ansible.py # SSH/Ansible endpoints
│ ├── services/ # Business logic layer
│ │ ├── __init__.py
│ │ ├── log_service.py # Log processing & compression
│ │ ├── device_service.py # Device management
│ │ ├── ansible_service.py # SSH/Ansible operations
│ │ └── file_service.py # File processing
│ ├── web/ # Web interface
│ │ ├── __init__.py
│ │ ├── main.py # Main dashboard routes
│ │ ├── devices.py # Device management UI
│ │ └── ansible.py # Ansible web interface
│ └── utils/ # Utility functions
│ ├── __init__.py
│ ├── database.py # DB utilities
│ ├── ssh_utils.py # SSH helpers
│ └── compression.py # Message compression
├── config/
│ ├── config.py # Configuration management
│ └── database_config.py # Database settings
├── templates/
│ ├── base.html # Base template
│ ├── dashboard.html # Enhanced dashboard
│ ├── ansible/ # Ansible interface templates
│ │ ├── inventory.html
│ │ ├── playbooks.html
│ │ └── execution.html
│ └── devices/ # Device management templates
├── ansible/
│ ├── playbooks/ # Ansible playbooks
│ ├── inventory/ # Dynamic inventory
│ └── roles/ # Custom roles
├── migrations/ # Database migrations
├── data/
│ ├── uploads/ # File uploads storage
│ └── backups/ # Database backups
└── main.py # Application entry point
Key Improvements
1. Better Database Structure
- Normalized database schema with separate tables
- Message aliases and compression
- File upload tracking
- Device metadata storage
2. Modular Architecture
- Separation of concerns (API, Web, Services, Models)
- Pluggable components
- Better testability
3. Enhanced Message Processing
- Message compression and aliases
- Efficient storage with references
- Client message size reduction
4. SSH/Ansible Integration
- Web-based Ansible interface
- Dynamic inventory management
- Playbook execution tracking
- SSH key management