Ensure the Login URL is using HTTPS

[dphiffer]

Description

One of our developers had a frustrating experience after following the login URL from vip dev-env info and found the resulting editing experience slightly broken when using the currently linked plaintext HTTP WordPress dashboard. This approach assumes there will be a working HTTPS connection available, which may not always be the case. But for the majority of our developers, offering an HTTPS login URL is better and would lead to reduced frustration.

Changelog Description

• Prefer HTTPS for dev environment login URL.

Changed

• Show both HTTP and HTTPS versions of the login URL.

Pull request checklist

• Update SETUP.md with any new environmental variables.
• Update the documentation.
• Manually test the relevant changes.
• Follow the pull request checklist
• Add/update automated tests as needed.

Steps to Test

1. Check out PR.
2. Run npm run build
3. Run npm link
4. Run ./dist/bin/vip.js dev-env info
5. Verify Login URL starts with https://

[Copilot]

Pull request overview

Prefers HTTPS for the dev-environment Login URL printed by vip dev-env info (and after vip dev-env start), while still surfacing the HTTP variant for environments without a working HTTPS proxy. The URL is now constructed via the WHATWG URL API so the autologin key is set as a proper query parameter and the protocol can be toggled cleanly.

Changes:

• Import EOL from node:os.
• Rebuild the login URL with new URL( frontEndUrl ) and set vip-dev-autologin via searchParams.
• Emit both the HTTPS and HTTP login URLs (HTTPS first), separated by EOL.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[sjinks]

Thank you!