-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
docs: clearly state that system.internal-url-prefix
shouldn't be changed
#3829
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
Conversation
…anged Happened today on Discord where a user changed internal-url-prefix and broke their instance. I think this should be stated clearer for new users and for non-native English speakers.
Ah, this explains why I had dejavu. I made the exact same PR a few years back. #3100 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #3829 +/- ##
=======================================
Coverage 99.45% 99.45%
=======================================
Files 3 3
Lines 183 183
=======================================
Hits 182 182
Misses 1 1 ☔ View full report in Codecov by Sentry. |
sentry/config.example.yml
Outdated
# Most of the time, this should NOT be changed. It's used for communication | ||
# between containers. `web` is the container's name, and `9000` is the | ||
# default port exposed by the Sentry image. If you want to change the | ||
# publicly exposed domain or port, you should probably change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# publicly exposed domain or port, you should probably change | |
# publicly exposed domain or port, you should change | |
# `system.url-prefix` above instead | |
# along with SENTRY_BIND in `.env` file. | |
# Also see https://develop.sentry.dev/self-hosted/#productionalizing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ughhh remind me a bit later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why? 😀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm juggling so many things at work 😂
Co-authored-by: Burak Yigit Kaya <byk@sentry.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I doubt someone misunderstands user interface here, but self-hosted interface or sentry interface is better IMHO.
Co-authored-by: Reinaldy Rafli <github@reinaldyrafli.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unblocking
Happened today on Discord where a user changed internal-url-prefix and broke their instance. I think this should be stated clearer for new users and for non-native English speakers.