docs(deploy): clarify running locally without dns #762
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
This adds some documentations about the issue where WDQS crashes when restarted with an empty database that never synced entities from MediaWiki. https://phabricator.wikimedia.org/T354266
…:wmde/wikibase-release-pipeline into T372177-improve-docs-for-running-locally
Member
|
Sorry, I was out sick. Looking at this now -- |
Member
|
I made the language a little bit clearer, but I have a thought on the technical side of things as an old DNS head. "example.com" is indeed publicly resolvable, just not to the thing people might want it to resolve to :) If we're going all the way out on a limb advising them to make /etc/hosts changes, we may want to suggest that they use either their own domain or a truly unresolvable domain like "yournamehere.wikibase". Just a thought -- |
Contributor
Author
|
So this is interesting. Even examples can be difficult 😄 I like your point. RFC2606 suggests to use e.g. |
This appears to be the more appropriate domain name to use as it explicitly targets DNS resolution related code. https://datatracker.ietf.org/doc/html/rfc2606#section-2
Contributor
Author
|
@datn done. Do you mind re-reviewing? |
lorenjohnson
pushed a commit
to lorenjohnson/wbs-deploy-setup
that referenced
this pull request
Aug 20, 2025
* docs(wdqs): details about the empty sync issue This adds some documentations about the issue where WDQS crashes when restarted with an empty database that never synced entities from MediaWiki. https://phabricator.wikimedia.org/T354266 * small edits to the new text * docs(deploy): clarify running locally without dns * T372177-improve-docs-for-running-locally clarified language just a tad * docs: switching example domain to .example tld This appears to be the more appropriate domain name to use as it explicitly targets DNS resolution related code. https://datatracker.ietf.org/doc/html/rfc2606#section-2 --------- Co-authored-by: Dan Shick <dan.shick@wikimedia.de>
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.
https://phabricator.wikimedia.org/T372177