mirror of
https://github.com/bugsink/bugsink.git
synced 2025-12-30 09:50:11 -06:00
a91fdcd656
My thinking: * Avoid Dependabot spam for harmless version bumps. (sentry-SDK has the most upgrades by an order of magnitude) * In princple, there should be no breakage, b/c they do semver and "minor version when you add functionality in a backward compatible manner" * This is dev tooling; it shouldn’t be a source of friction. * As it stands: I'm not thoroughly reviewing these anyway (b/c of the spammyness) The alternative would have been to "just freeze" it; if we ever run into problems because of the unpinning I certainly will.
Bugsink: Self-hosted Error Tracking
Screenshot
Installation & docs
The quickest way to evaluate Bugsink is to spin up a throw-away instance using Docker:
docker pull bugsink/bugsink:latest
docker run \
-e SECRET_KEY=PUT_AN_ACTUAL_RANDOM_SECRET_HERE_OF_AT_LEAST_50_CHARS \
-e CREATE_SUPERUSER=admin:admin \
-e PORT=8000 \
-p 8000:8000 \
bugsink/bugsink
Visit http://localhost:8000/, where you'll see a login screen. The default username and password
are admin.
Now, you can set up your first project and start tracking errors.
Detailed installation instructions are on the Bugsink website.