mirror of
https://github.com/jlengrand/bugsink.git
synced 2026-03-10 08:01:17 +00:00
488d0190bb
* Rebuilding the image will not accidentally assign a different UID to `bugsink` this would be "extremely annoying" in the context of bind-mounts and volumes. * Ensures predictable ownership for bind-mounts and Docker volumes at build time. * Avoids collisions with existing host accounts Considerations for 14237: * well below the 65535 limit, keeping it compatible with default subuid/subgid mappings. * Positioned above 1000 to steer clear of standard system and regular user ranges. * Not so large that older filesystems or tooling (e.g., simple NFS exports) might have issues. See #176
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.