[i18nIgnore] feat: change default port

[ematipico]

What kind of changes does this PR include?

• New or updated content

Description

This PR changes the default port to 4321.

Code PR: withastro/astro#7874

I only did a search and replace of :3000 throughout the website. Let me know if the change is too disruptive and if I should change only a subset of pages.

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	ca6e039
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/64ef4392ff8b260008c0ca12
😎 Deploy Preview	https://deploy-preview-3977--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ElianCodes]

Just left a couple of changes, mostly generalising the use of http://localhost:4321 instead of localhost:4321 or https://localhost:4321

Sorry in advance 🤣

[ematipico]

@ElianCodes I leave the task to merge the suggestions to you :)

[ElianCodes]

@ematipico allright! Can you confirm that the port will default to 4322 instead of 4321 when that port is occupied?

[ematipico]

@ematipico allright! Can you confirm that the port will default to 4322 instead of 4321 when that port is occupied?

Yes :)

Same behaviour as before. Astro starts looking for the first port available, incrementally: 4321, 4322, 4323, etc.

[ElianCodes]

Hey @ematipico! I'm in the process of generalising the protocol. Gonna go through all of them one last time.

When I'm done, I'll keep you posted!

[ElianCodes]

Found a couple of leftovers 😱

[ElianCodes]

I think I now should have all of them! Good to go!

[sarah11918]

WHEW! 😅

Assuming that there is otherwise no language changed here on any of the pages, just 3000 -> 4321, then I'm approving this one as ready for v3!

(If there is anything other than that I should take a peek at, please point it out to me. Otherwise, this one just waits!)

[ematipico]

WHEW! 😅

Assuming that there is otherwise no language changed here on any of the pages, just 3000 -> 4321, then I'm approving this one as ready for v3!

(If there is anything other than that I should take a peek at, please point it out to me. Otherwise, this one just waits!)

@sarah11918

@ElianCodes changed all the instances of localshost to http://localhost. It wasn't part of the original PR.

[yanthomasdev]

🚨 IMPORTANT 🚨

Till this PR gets merged we will probably have more pages with localhost:3000, especially in translations. From what I can see, this PR only changes the mentions of the port, no new docs added, so the final merge message should contain [i18nIgnore] to avoid our tracker from marking these pages as 100% updated, and also rerun the search and replace to account for newer translations added.

[sarah11918]

@yan-thomas I'm changing most of these PRs to PR the upgrade guide v3 branch instead of main, so does that solve the above problem? Let me know how we should handle this one! Maybe an intentional rescan in that PR branch shortly before merging, and then we might catch all of them?

[yanthomasdev]

@yan-thomas I'm changing most of these PRs to PR the upgrade guide v3 branch instead of main, so does that solve the above problem?

No! Keep this PR to main, after the 3.0 PR is merged then update branch and search and replace localhost:3000 here, and then you're allowed to merge here! With [i18nIgnore]