Skip to content

Conversation

@iamrajjoshi
Copy link
Contributor

cleaned up the instructions for slack and msteams installation for development

@iamrajjoshi iamrajjoshi requested a review from a team January 2, 2025 16:15
@iamrajjoshi iamrajjoshi self-assigned this Jan 2, 2025
@vercel
Copy link

vercel bot commented Jan 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
develop-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 6, 2025 7:12pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
changelog ⬜️ Ignored (Inspect) Visit Preview Jan 6, 2025 7:12pm
sentry-docs ⬜️ Ignored (Inspect) Visit Preview Jan 6, 2025 7:12pm

@cathteng cathteng requested a review from a team January 2, 2025 16:17
Copy link
Member

@cathteng cathteng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

questions

```
**NOTE**: If you're doing local Sentry development, you should use a tool like Ngrok and add `system.url-prefix: "https://<your_subdomain>.ngrok.io"` to your `~/.sentry/config.yml`. Otherwise, installing the Discord bot won't work, as it will not be able to communicate with your local Sentry instance.
**NOTE**: If you're doing local Sentry development, you should use a tool like Ngrok and use `getsentry` repo when starting your Sentry server. Otherwise, installing the Discord bot won't work, as it will not be able to communicate with your local Sentry instance.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we still need to use ngrok right? does it matter if you use getsentry or sentry if you use ngrok?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the getsentry repo is where the Ngrok config is more actively maintained and will have everything preconfigured and setup so u don't need to modify stuff like url-prefix which has been janky in the past. i have linked the ngrok docs i wrote under the diff here with more details

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the getsentry repo is where the Ngrok config is more actively maintained and will have everything preconfigured and setup so u don't need to modify stuff like url-prefix which has been janky in the past.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i updated this since we fixed the sentry ngrok presets

```
**NOTE**: If you're doing local Sentry development, you should use a tool like Ngrok and add `system.url-prefix: "https://<your_subdomain>.ngrok.io"` to your `~/.sentry/config.yml`, otherwise, installing the Slack APP will complain because the redirect URI points to `localhost:8000`. Also, install the Slack integration from the ngrok subdomain or it will fail to install.
If you a Sentry employee, you can set the `slack.client-id` and `slack.client-secret` in `devlocal.py` inside `getsentry` instead.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is devlocal.py only a sentry employee thing or can anyone add it and use it for local dev?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its a sentry employee thing. i had to think about this for a while, whether i should mention it here, but i felt it was ok because we explain the difference between sentry and getsentry

https://develop.sentry.dev/application-architecture/sentry-vs-getsentry/

Copy link
Contributor

@coolguyzone coolguyzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating!

@iamrajjoshi iamrajjoshi merged commit 95b7e02 into master Jan 7, 2025
10 checks passed
@iamrajjoshi iamrajjoshi deleted the raj/cleanup-slack-dev-docs branch January 7, 2025 17:19
@github-actions github-actions bot locked and limited conversation to collaborators Jan 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants