Notification History Feature

[Illyism]

Added a comprehensive notification history system that stores and displays all notifications sent through any channel (Discord, Email, Telegram, Slack, Pushover, Webhook).

Database

• New Migration: create_notification_history_table.php
  • Stores notification metadata including team, notification type, event type, channel, title, message, and JSON metadata
  • Includes indexes for efficient querying by team, event type, and channel
  • Tracks when notifications were sent

Models

• New Model: NotificationHistory
  • Eloquent model with relationships to Team
  • Proper fillable fields and casts for JSON metadata

Event Listener

• New Listener: StoreNotificationHistory
  • Automatically captures all notifications via Laravel's NotificationSent event
  • Extracts title, message, and metadata from notifications across all channels
  • Channel-agnostic - works with Discord, Email, Telegram, Slack, Pushover, and Webhook
  • Safely handles errors without breaking notification delivery
  • Registered in EventServiceProvider

Livewire Component

• New Component: Notification/History
  • Displays paginated list of all notifications for the current team
  • Filtering by channel and event type
  • Pagination (50 per page)
  • Real-time updates via Livewire

Views

• New View: livewire/notification/history.blade.php
  • Clean, modern UI matching Coolify's design system
  • Displays notification details including title, message, channel badges, and metadata
  • Shows links to related resources (deployments, applications, etc.)
  • Responsive design with proper dark mode support

Routes

• New Route: /notifications → NotificationHistory component
  • Accessible at /notifications
  • Named route: notification.history

Navigation

• Updated: navbar.blade.php
  • Added "Notification History" menu item
  • Separated from "Notification Settings" for clarity
  • Proper active state highlighting

Helpers

• New Helper Function: store_notification_history()
  • Centralized function for storing notifications
  • Handles errors gracefully
  • Located in bootstrap/helpers/notifications.php

Technical Details

Event-Driven Architecture

The notification history is stored automatically via Laravel's event system. When any notification is sent through any channel, the NotificationSent event is fired, and our listener captures it. This ensures:

• Separation of concerns: Storage logic is separate from notification channels
• No code duplication: One listener handles all channels
• Automatic: No need to modify individual notification channels
• Reliable: Errors in storage don't break notification delivery

Channel Support

The listener intelligently extracts information from notifications by calling their channel-specific methods:

• Discord: Extracts title and description from toDiscord()
• Slack: Extracts title and description from toSlack()
• Pushover: Extracts title and message from toPushover()
• Telegram: Extracts message from toTelegram()
• Email: Extracts subject from toMail()
• Webhook: Extracts data from toWebhook()

Metadata Extraction

The listener automatically extracts common metadata from notifications:

• Application name, UUID, and FQDN
• Deployment UUID and URL
• Project UUID and name
• Environment UUID and name
• Any other properties available on the notification object

Event Type Mapping

Notifications are automatically categorized into event types:

• deployment_success, deployment_failure
• backup_success, backup_failure
• status_change
• scheduled_task_success, scheduled_task_failure
• docker_cleanup_success, docker_cleanup_failure
• server_disk_usage, server_reachable, server_unreachable
• server_patch, traefik_outdated
• server_force_enabled, server_force_disabled
• general, test, ssl_certificate_renewal, hetzner_deletion_failure

User Experience

Users can now:

1. View all notifications sent to their team in one centralized location
2. Filter notifications by channel (Discord, Email, etc.) or event type
3. See notification details including title, message, and related resources
4. Access links to deployments, applications, and other related resources directly from notifications
5. Browse notification history with pagination

Backwards Compatibility

• ✅ Fully backwards compatible
• ✅ No breaking changes to existing notification channels
• ✅ No changes to existing notification sending logic
• ✅ New feature only - doesn't affect existing functionality

[Illyism]

Need a good test for all existing notification types

but I don't have time