Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple project support #139

Closed
butschster opened this issue Apr 26, 2024 · 1 comment · Fixed by buggregator/server#150
Closed

Multiple project support #139

butschster opened this issue Apr 26, 2024 · 1 comment · Fixed by buggregator/server#150
Assignees
Labels
enhancement New feature or request for contributors Extra attention is needed
Milestone

Comments

@butschster
Copy link
Member

Discussed in https://github.com/orgs/buggregator/discussions/148

Originally posted by indykoning April 26, 2024
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:

  • auth username and/or password (Ray, SMTP, Profiler. Inspector, Sentry, Http Dumps)
  • url variable (Inspector, Sentry)
  • ? (monolog, VarDumper)

e.g. Profiler also supports an application name & Inspector supports an ingestion key

@butschster butschster added the enhancement New feature or request label Apr 26, 2024
@butschster butschster self-assigned this Apr 26, 2024
butschster referenced this issue in buggregator/server Apr 26, 2024
@butschster butschster linked a pull request Apr 27, 2024 that will close this issue
@butschster butschster reopened this Apr 29, 2024
@butschster butschster transferred this issue from buggregator/server May 3, 2024
@butschster butschster added this to the 1.0 milestone May 3, 2024
@butschster butschster added the for contributors Extra attention is needed label May 3, 2024
@butschster butschster linked a pull request May 9, 2024 that will close this issue
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 13, 2024
Kreezag added a commit that referenced this issue Jul 15, 2024
Kreezag added a commit that referenced this issue Jul 15, 2024
Kreezag added a commit that referenced this issue Jul 15, 2024
Kreezag added a commit that referenced this issue Jul 15, 2024
Kreezag added a commit that referenced this issue Jul 26, 2024
Kreezag added a commit that referenced this issue Jul 26, 2024
Kreezag added a commit that referenced this issue Jul 27, 2024
Kreezag added a commit that referenced this issue Jul 27, 2024
Kreezag added a commit that referenced this issue Jul 27, 2024
Kreezag added a commit that referenced this issue Jul 28, 2024
Kreezag added a commit that referenced this issue Jul 28, 2024
@Kreezag
Copy link
Member

Kreezag commented Jul 28, 2024

Need to implement #212 before close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request for contributors Extra attention is needed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants