-
Notifications
You must be signed in to change notification settings - Fork 461
Notifications
Henne Vogelsang edited this page Apr 22, 2020
·
28 revisions
Details about our notification sub-system.
This sub-system is based on the Event, Subscription and Notification classes.
An Event describes things that happen throughout the whole OBS (backend+frontend). See the Events page for deeper information about Event.
A Subscription is specific for a User, a type of Event (eventtype=Event::CommentForPackage), a Role the User might have (receiver_role="maintainer") and the place where it should be displayed (channel=web)
- OBS admins can create app wide defaults (
EventSubscription.where(user_id: nil)) - A
Usercan have a collection ofSubscriptionthat overwrites those defaults
A Notification is for a specific Event, a User (subscriber_id=1) and one or more places where it should be displayed (rss=true, web=false)
- An
Eventgets stored in the database -
clockworkperiodically schedules aSendEventEmailsJob -
SendEventEmailsJobgoes over theEventtable and- sends e-mail for all
Eventthat have email subscribers - creates
Notificationfor allEventthat have web/rss subscribers
- sends e-mail for all
- Development Environment Overview
- Development Environment Tips & Tricks
- Spec-Tips
- Code Style
- Rubocop
- Testing with VCR
- Test in kanku
- Authentication
- Authorization
- Autocomplete
- BS Requests
- Events
- ProjectLog
- Notifications
- Feature Toggles
- Build Results
- Attrib classes
- Flags
- The BackendPackage Cache
- Maintenance classes
- Cloud uploader
- Delayed Jobs
- Staging Workflow
- StatusHistory
- OBS API
- Owner Search
- Search
- Links
- Distributions
- Repository
- Data Migrations
- Package Versions
- next_rails
- Ruby Update
- Rails Profiling
- Remote Pairing Setup Guide
- Factory Dashboard
- osc
- Setup an OBS Development Environment on macOS
- Run OpenQA smoketest locally
- Responsive Guidelines
- Importing database dumps
- Problem Statement & Solution
- Kickoff New Stuff
- New Swagger API doc
- Documentation and Communication
- GitHub Actions
- Brakeman
- How to Introduce Software Design Patterns
- Query Objects
- Services
- View Components
- RFC: Core Components
- RFC: Decorator Pattern
- RFC: Backend models
- RFC: Hotwire Turbo Frames Pattern