Proberaum for Backstage

Scheduler Notifications

Send recurring notifications (cron or interval based) to users and groups, defined as entities in the catalog.

ExperimentalEarly stage

Packages

@proberaum/backstage-plugin-catalog-backend-module-scheduler-notifications

Backend modulenpm v0.4.0source

The scheduler-notifications backend module for the catalog plugin.

Installation

Terminal
# From your Backstage root directory
yarn --cwd packages/backend add @proberaum/backstage-plugin-catalog-backend-module-scheduler-notifications
packages/backend/src/index.ts
const backend = createBackend();
// ...
backend.add(import('@proberaum/backstage-plugin-catalog-backend-module-scheduler-notifications'));
README

The scheduler-notifications backend module for the catalog plugin.

This plugin was created through the Backstage CLI

@proberaum/backstage-plugin-scheduler-notifications-backend

Backend pluginnpm v0.4.0source

Installation

Terminal
# From your Backstage root directory
yarn --cwd packages/backend add @proberaum/backstage-plugin-scheduler-notifications-backend
packages/backend/src/index.ts
const backend = createBackend();
// ...
backend.add(import('@proberaum/backstage-plugin-scheduler-notifications-backend'));
README

This plugin backend was templated using the Backstage CLI. You should replace this text with a description of your plugin backend.

Installation

This plugin is installed via the @proberaum/backstage-plugin-scheduler-notifications-backend package. To install it to your backend package, run the following command:

Terminal window
# From your root directory
yarn --cwd packages/backend add @proberaum/backstage-plugin-scheduler-notifications-backend

Then add the plugin to your backend in packages/backend/src/index.ts:

const backend = createBackend();
// ...
backend.add(
  import('@proberaum/backstage-plugin-scheduler-notifications-backend'),
);

Development

This plugin backend can be started in a standalone mode from directly in this package with yarn start. It is a limited setup that is most convenient when developing the plugin backend itself.

If you want to run the entire project, including the frontend, run yarn start from the root directory.