-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
fix(init): change initial site URL to one that is safe for the future #9133
Conversation
✅ [V2]Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
@@ -14,7 +14,7 @@ const config = { | |||
favicon: 'img/favicon.ico', | |||
|
|||
// Set the production url of your site here | |||
url: 'https://your-docusaurus-test-site.com', | |||
url: 'https://your-docusaurus-site.example', |
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.
Maybe use .example.com
? Seems more unsurprising.
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.
@Josh-Cena Not so terrible, but it looks longer than .example
.
A candidate is your-docusaurus-site.example.com
or docusaurus-site.example.com
.
https://example.com & https://www.example.com are resolved to an example page by IANA, but pages for the other subdomains don't seem to be prepared.
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.
It's okay if the page is a broken page. And yes, I meant your-docusaurus-site.example.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.
Ok, I'll rename all of them.
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.
@Josh-Cena Done.
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.
Almost good. Could you revert the changes in examples/
? These are autogenerated. Also I think some fixtures have an extra trailing line break; I'm enabling the tests to see if they still pass.
@Josh-Cena Are these 2 all, aren't they? |
RFC 2606 reserves the `.example` domain for illustrative purposes.
Yes |
@Josh-Cena Done |
Why did the Build Performance CI task fail? |
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.
Since the other tests are passing, this is fine. The build performance action is not very stable anyway.
Thanks. We can cherry-pick this in the v2 branch. |
Damn, we live in a crazy world 😅 thanks for noticing this and fixing it |
Pre-flight checklist
Motivation
The current initial template specifies
https://your-docusaurus-test-site.com
for the site URL. This is used for OGP contents. Everyone can reserve this domain and an organization (or person) related to casino in Turkey has already done.https://www.virustotal.com/gui/url/e8aeabbb3b02e8c207176c74dbf41fbf807fbf4be6f45c7f6ff9a139417ec181/details
https://otx.alienvault.com/indicator/domain/your-docusaurus-test-site.com
RFC 2606 reserves the
.example
domain for illustrative purposes. (See the Section 2) We have to use this instead. (.test
orexample.{com,org,net}
are also OK)Test Plan
Test links
Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs