Multiple project support #148
Replies: 3 comments 2 replies
-
For vardumps, I can add a hostname or any other context in case of using |
Beta Was this translation helpful? Give feedback.
-
Yeah, we used to have project support, but then I did a big refactor and had to disable it. Check out HandleReceivedEvent in that command – you'll see there's a project ID property. Right now, we're putting together guidelines on how to contribute and get involved with Buggregator development. If you've got some free time, we'd love to have you on board. It'd be awesome if you could create an issue at least, and I'll make sure it gets added to our roadmap. The frontend development is a bit tricky because it's not syncing up with the server side as smoothly as we'd like. Managing the project list from the frontend is a bit of a headache. I'm thinking of adding support to handle it using |
Beta Was this translation helpful? Give feedback.
-
Hi @indykoning! I've just released a beta release of Buggregator: link to GitHub release. You can install it with the |
Beta Was this translation helpful? Give feedback.
-
When developing multiple applications for a single project this works fantastic, not only aggregating the different outputs from debugging software but also aggregating of these for the applications so you have a good timeline of what each application was up to when debugging.
Running this locally you have no choice but aggregate every project into the same overview, unless you run multiple buggregator instances on different ports.
I think it would be nice to have a dropdown to switch projects in buggregator, kind of like how you can have different projects in Sentry.
Some ways we could separate events into projects are:
e.g. Profiler also supports an application name & Inspector supports an ingestion key
Beta Was this translation helpful? Give feedback.
All reactions