Improved alterting and TZ handling

This commit is contained in:
James Pattinson
2025-10-23 15:56:54 +00:00
parent c1accd82c5
commit ad370f41ed
2 changed files with 103 additions and 51 deletions

View File

@@ -116,13 +116,16 @@ To migrate data from the old system:
2. Transform to new schema format
3. Import into the new system
## Security
## Time Zone Handling
- JWT token authentication
- Password hashing with bcrypt
- Input validation with Pydantic
- SQL injection protection via SQLAlchemy ORM
- CORS configuration for frontend integration
The system uses UTC (Coordinated Universal Time) as the standard for all time storage and display in aviation contexts:
- **Database Storage**: All times are stored in UTC
- **Admin Console Display**: Times are displayed in UTC (with Z suffix)
- **Data Entry**: Times are entered as local time in the New PPR entry form, then automatically converted to UTC for storage
- **API**: All datetime fields in API responses are UTC ISO strings
This ensures consistency across different time zones and complies with aviation standards where UTC is the international standard.
## Performance