Files

T

blam f326c2ee1e Merge branch 'master' of github.com:spotify/backstage into feat/backend-plugin

* 'master' of github.com:spotify/backstage: (30 commits)
  fix(techdocs-core): use the content of the readme as long description for the pypi package (#2578)
  chore: add contrib to CONTRIBUTING.md (#2585)
  Fix typo (#2584)
  backend-common: default config env to development
  v0.1.1-alpha.23
  TechDocs: Inject CSS transformer and initial backstage style integration for reader (#2560)
  bug(gql): use import to import the graphql module
  Rename file
  [blog] Announce CNCF Sandbox (#2568)
  document cleaning - tutorial quickstarts (#2520)
  Simplify codecov flag names
  chore(scaffolder-backend): typo in visibility
  Kubernetes plugins boilerplate (#2559)
  CHANGELOG: add entry for SessionApi refactor
  Upload package specific code coverage to codecov
  Add codecov flags for core and core-api packages
  TechDocs: Enable allowVulnerableTags in sanitize-html (#2554)
  chore: trust the Boolean :)
  docs: regenerate api reference docs
  core: refactor SessionStateApi to SessionApi with sign-in/out
  ...

2020-09-24 10:54:04 +02:00

dev

Fix linter errors and warnings in sentry plugin

2020-05-20 12:12:58 +02:00

src

Refactor the Sentry plugin router

2020-09-04 13:58:34 +02:00

.eslintrc.js

Add Sentry plugin front-end

2020-05-20 12:12:57 +02:00

package.json

Merge branch 'master' of github.com:spotify/backstage into feat/backend-plugin

2020-09-24 10:54:04 +02:00

README.md

docs: fix broken links

2020-08-11 12:21:15 +02:00

README.md

sentry

Welcome to the sentry plugin!

This plugin was created through the Backstage CLI

Getting started

Your plugin has been added to the example app in this repository, meaning you'll be able to access it by running yarn start in the root directory, and then navigating to /sentry.

You can also serve the plugin in isolation by running yarn start in the plugin directory. This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads. It is only meant for local development, and the setup for it can be found inside the /dev directory.

Needs SENTRY_TOKEN set in the environment for the backend to startup

export SENTRY_TOKEN=<INSERT_SENTRY_TOKEN_HERE>