- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control. - Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities. - Created .gitmodules to include OpenZeppelin contracts as a submodule. - Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment. - Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks. - Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring. - Created scripts for resource import and usage validation across non-US regions. - Added tests for CCIP error handling and integration to ensure robust functionality. - Included various new files and directories for the orchestration portal and deployment scripts.
1.5 KiB
1.5 KiB
WSL2 Access Instructions
Issue
When running Vite dev server in WSL2, localhost from Windows browser may not connect.
Solutions
Option 1: Use WSL IP Address (Recommended)
-
Find your WSL IP address:
hostname -I # or ip addr show eth0 | grep "inet " -
Access the server using the WSL IP:
http://<WSL_IP>:5173Example:
http://172.20.10.2:5173
Option 2: Use localhost with Port Forwarding
Windows automatically forwards localhost to WSL, but sometimes you need to:
-
In Windows PowerShell (as Administrator):
netsh interface portproxy add v4tov4 listenport=5173 listenaddress=0.0.0.0 connectport=5173 connectaddress=<WSL_IP> -
Then access:
http://localhost:5173
Option 3: Use Windows Hostname
Try accessing via Windows hostname:
http://$(hostname).local:5173
Option 4: Check Windows Firewall
If still not working, check Windows Firewall:
- Windows Defender Firewall → Advanced Settings
- Inbound Rules → New Rule
- Allow port 5173
Current Configuration
The Vite server is configured with:
host: '0.0.0.0'- Allows external connectionsport: 5173- Standard Vite port
Quick Test
Test if server is accessible:
# From WSL
curl http://localhost:5173
# From Windows PowerShell
curl http://localhost:5173
Alternative: Use Windows Terminal
If you're using Windows Terminal, you can right-click the tab and select "Open in new tab" to open the URL directly.