Changed domain name setting to not show example.com but the actual domain name defined in the .env #1965
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…main name defined in the .env
|
How is the domain name wrong in the emails? It depends on the setting? For instance, the production server does produce activation emails with |
|
It didn't work on another instance I made, it still produced example.com links even when configured with a correct DNS |
Rebase domainNameFix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A brief description of the purpose of the changes contained in this PR.
Changed domain name setting to not show example.com but the actual domain name defined in the .env.
Now, the correct domain name will be shown in the Django logs as well as in emails sent.
Issues this PR resolves
#1917 (partial)
A checklist for hand testing
Checklist