/sentry

Sentry is a cross-platform crash reporting and aggregation platform.

MIT LicenseMIT

Sentry
Sentry

This is the snap for Sentry. It works on Ubuntu, Fedora, Debian, and other major Linux distributions.

Snap Status

Published for with 💝 by Snapcrafters

Install

Before installing, make sure you have the following availiable:

  • Postgres database.
  • Redis database.

Once you have these running, install Sentry with: sudo snap install sentry

(Don't have snapd installed?)

This will install 4 things:

  • A sentry command to allow you to configure Sentry.
  • 3 daemons, consisting of web, worker and cron.

The daemons can be accessed via systemctl, there names being:

  • snap.sentry.web
  • snap.sentry.worker
  • snap.sentry.cron

At this point, we can initialise Sentry:

sudo sentry init

Note sudo. This is because the daemons will be running as root (although confined by snapd). If you run this without sudo, the running Sentry daemons won't be able to find the configuration files.

At this point, you can go and edit Sentry's config files to point them at your Postgres and Redis databases. You can find the location of these files with:

sudo sentry config discover

Once edited, you need to run all pending migrations and setup a superuser with:

sudo sentry upgrade

Afterwards, restart the daemons with:

sudo systemctl restart "snap.sentry.*"

Now, you should be able to browse to http://localhost:9000

Remaining tasks

Snapcrafters (join us) are working to land snap install documentation and the snapcraft.yaml upstream so Sentry can authoritatively publish future releases.

  • Fork the Snapcrafters template repository to your own GitHub account
  • Rename the forked Snapcrafters template repository
  • Update logos and references to [Project] and [my-snap-name]
  • Create a snap that runs in devmode
  • Register the snap in the store, using the preferred upstream name
  • Add a screenshot to this README.md
  • Publish the devmode snap in the Snap store edge channel
  • Add install instructions to this README.md
  • Update snap store metadata, icons and screenshots
  • Convert the snap to strict confinement, or classic confinement if it qualifies
  • Publish the confined snap in the Snap store beta channel
  • Update the install instructions in this README.md
  • Post a call for testing on the Snapcraft Forum - link
  • Request your GitHub repository is forked to the Snapcrafters organisation and configured for automated builds
  • Add the provided Snapcraft build badge to this README.md
  • Publish the snap in the Snap store stable channel
  • Update the install instructions in this README.md
  • Post an announcement in the Snapcraft Forum - link
  • Submit a pull request or patch upstream that adds snap install documentation - link
  • Submit a pull request or patch upstream that adds the snapcraft.yaml and any required assets/launchers - link
  • Add upstream contact information to the README.md
  • If upstream accept the PR:
    • Request upstream create a Snap store account
    • Contact the Snap Advocacy team to request the snap be transferred to upstream
  • Ask the Snap Advocacy team to celebrate the snap - link

If you have any questions, post in the Snapcraft forum.

The Snapcrafters

Joe Borg
Joe Borg