artin/webarena
1
0
Fork 0
mirror of https://github.com/web-arena-x/webarena.git synced 2026-02-06 11:16:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove hardcoded IPs from documentation

Browse Source 
- Update environment_docker/README.md to use YOUR_MAP_BACKEND_IP placeholder
- Make documentation more generic for users setting up their own servers
- Only CI workflow and internal notes still contain specific IP

Co-authored-by: openhands <openhands@all-hands.dev>
This commit is contained in:
openhands 2025-09-02 15:32:02 +00:00
parent 85f7dcbcdd
commit 48d6a98137
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
environment_docker/README.md
View File

@ -30,9 +30,9 @@ ID: ami-08a862bf98e3bd7aa
3. **Map Backend Configuration**: Add the following to your instance's user data to automatically configure the map backend:
```
MAP_BACKEND_IP=18.208.187.221
MAP_BACKEND_IP=YOUR_MAP_BACKEND_IP
```
This will automatically configure the frontend to use the current AWS tile server.
Replace `YOUR_MAP_BACKEND_IP` with your map backend server's IP address.
4. Create an Elastic IP and bind to the instance to associate the instance with a static IP and hostname. Take note of the hostname, usually in the form of "ec2-xx-xx-xx-xx.us-east-2.compute.amazonaws.com". This will be used as "<your-server-hostname>" in the following commands.
@ -192,7 +192,7 @@ The homepage will be available at `http://<your-server-hostname>:4399`.
### Map
The WebArena AMI automatically configures the map frontend to use the current AWS tile server when you set `MAP_BACKEND_IP=18.208.187.221` in the user data (as shown in step 3 above). No manual configuration is required.
The WebArena AMI automatically configures the map frontend to use your specified map backend server when you set `MAP_BACKEND_IP=YOUR_MAP_BACKEND_IP` in the user data (as shown in step 3 above). No manual configuration is required.
#### Setting up your own map backend