Skip to content

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

Merged
merged 4 commits into from
Jul 25, 2025

Conversation

aldy505
Copy link
Collaborator

@aldy505 aldy505 commented Jul 23, 2025

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.

…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.
@aldy505
Copy link
Collaborator Author

aldy505 commented Jul 23, 2025

Ah, this explains why I had dejavu. I made the exact same PR a few years back. #3100

Copy link

codecov bot commented Jul 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.45%. Comparing base (abe34d0) to head (840df4b).
Report is 1 commits behind head on master.

✅ 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.
📢 Have feedback on the report? Share it here.

# 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
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
# 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

Copy link
Collaborator Author

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

Copy link
Member

Choose a reason for hiding this comment

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

Why? 😀

Copy link
Collaborator Author

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>
Copy link
Collaborator

@aminvakil aminvakil left a 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>
Copy link
Member

@BYK BYK left a comment

Choose a reason for hiding this comment

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

Unblocking

@aldy505 aldy505 enabled auto-merge (squash) July 25, 2025 03:10
@aldy505 aldy505 merged commit 79f18ee into master Jul 25, 2025
11 checks passed
@aldy505 aldy505 deleted the aldy505/docs/clear-internal-url-prefix branch July 25, 2025 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants