Files
myeasycms-v2/packages/database-webhooks
Giancarlo Buomprisco 4a47df81db Registry API Refactoring (#144)
* Refactor core to use a flexible registry pattern

- Introduce a new registry mechanism for mailer providers
- Extract mailer provider enum to a separate file
- Implement dynamic mailer loading using a registry
- Update package dependencies and exports
- Improve modularity and extensibility of mailer implementation

* Refactor monitoring and billing services to use a flexible registry pattern

- Introduce a shared registry mechanism for dynamic service loading
- Replace static switch-based implementations with a registry-based approach
- Update instrumentation, CMS, and monitoring services to use the new registry
- Improve modularity and extensibility of service implementations
- Add Zod-based type-safe provider validation

* Simplify async registration in monitoring and billing services

- Remove unnecessary async wrappers for no-op registrations
- Update type definitions to support both async and sync registration functions
- Standardize registration approach for Paddle and Sentry providers

* Remove Tailwind package from packages where it is not being needed

* Remove Tailwind config references from pnpm-lock.yaml

* Update instrumentation registry to support dynamic monitoring providers

- Modify type definition to use NonNullable MonitoringProvider
- Import MonitoringProvider type from get-monitoring-provider
- Enhance type safety for instrumentation registration
2025-02-05 18:38:43 +08:00
..
2025-02-05 18:38:43 +08:00
2024-03-30 14:51:16 +08:00

Database Webhooks - @kit/database-webhooks

This package is responsible for handling webhooks from database changes.

For example:

  1. when an account is deleted, we handle the cleanup of all related data in the third-party services.
  2. when a user is invited, we send an email to the user.
  3. when an account member is added, we update the subscription in the third-party services

The default sender provider is directly from the Postgres database.

WEBHOOK_SENDER_PROVIDER=postgres

Should you add a middleware to the webhook sender provider, you can do so by adding the following to the WEBHOOK_SENDER_PROVIDER environment variable.

WEBHOOK_SENDER_PROVIDER=svix

For example, you can add [https://docs.svix.com/quickstart]](Swix) as a webhook sender provider that receives webhooks from the database changes and forwards them to your application.

Svix is not implemented yet.