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

Write a doc that explains all of the parts of Sentry #789

Open
1 task
chadwhitacre opened this issue Jan 4, 2021 · 3 comments
Open
1 task

Write a doc that explains all of the parts of Sentry #789

chadwhitacre opened this issue Jan 4, 2021 · 3 comments

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Jan 4, 2021

I've seen a few times recently where people have basically asked "What are all these moving parts? Do I really need them all?" Here's the latest example from @kanadaj:

do u think better docs on that would help?

Yeah, definitely, both on the exact role of the individual services (there is around 10 and I don't even know the exact data path for different kinds of stuff) [...]

We generally point people to the architecture diagram, but I think we could do better about connecting the dots between that and the docker-compose.yml.

Todo

+1

  1. Wajahatlateef - forum
  2. Am2020 - forum
@max-wittig
Copy link
Contributor

That would be really nice +1 for that @dlouzan

@dlouzan
Copy link

dlouzan commented Jan 7, 2021

This is a very nice initiative, it would maybe help us understand the issues we have on #783 🙇 Of course one can read the source code, but decent architecture and flow docs would probably go a long way.

@github-actions
Copy link

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

5 participants