Fix the "pg_resetwal: error: cannot be executed by "root"
pg_resetwal: You must run pg_resetwal as the PostgreSQL superuser." error when running `docker exec gitlab /opt/gitlab/embedded/bin/pg_resetwal -f /var/opt/gitlab/postgresql/data`
- 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>
- Add back the recommended approach for setting up your own map backend
- Include step-by-step instructions for launching Ubuntu instance with boot-init script
- Reference webarena-map-backend-boot-init.yaml for automated setup
- Explain how to integrate custom backend with the new AMI using MAP_BACKEND_IP
- Keep instructions concise but complete for production deployments
Users now have clear guidance for both using existing AWS infrastructure
and setting up their own map backend infrastructure.
Co-authored-by: openhands <openhands@all-hands.dev>
- Remove complex multiple options and manual setup instructions
- Focus on the new, easy approach using the updated AMI
- Reference webarena-map-backend-boot-init.yaml for users who want their own backend
- Eliminate 100+ lines of complex manual setup instructions
- Make documentation much more user-friendly and focused
The new approach is simple: use the AMI with MAP_BACKEND_IP environment variable.
For custom backends, users can follow the automated boot-init script.
Co-authored-by: openhands <openhands@all-hands.dev>
- Replace ami-06290d70feea35450 with ami-08a862bf98e3bd7aa as the default AMI
- Add automatic map configuration instructions in main setup steps
- Simplify map section - no manual configuration needed with new AMI
- Remove separate NEW_AMI_README.md file - integrated into main docs
- Add legacy note for users still using the original AMI
The new AMI automatically configures map backend URLs via MAP_BACKEND_IP
environment variable, eliminating the need for manual configuration.
Co-authored-by: openhands <openhands@all-hands.dev>
✅ Created AMI: ami-08a862bf98e3bd7aa (us-east-2)
✅ Automatic frontend configuration via MAP_BACKEND_IP environment variable
✅ No manual configuration required - fully automated setup
✅ Defaults to current AWS tile server (18.208.187.221)
✅ Includes comprehensive documentation and test scripts
Features:
- Cloud-init script automatically configures map URLs on boot
- Environment variable control for easy backend switching
- Automatic service restart after configuration
- Configuration logging for troubleshooting
- Backward compatible with existing deployments
Files added:
- webarena-frontend-map-config.yaml: Cloud-init configuration
- create-webarena-ami-with-map-fix.sh: AMI creation script
- test-new-ami.sh: AMI testing script
- NEW_AMI_README.md: Complete usage documentation
Updated README to recommend new AMI as primary option with fallback to manual configuration.
Co-authored-by: openhands <openhands@all-hands.dev>
- Remove optional AMI creation instructions
- Keep focus on essential frontend configuration
- AMI creation will be handled by maintainers
Co-authored-by: openhands <openhands@all-hands.dev>
- Add optional section for creating new AMI with map backend fixes
- Include AWS AMI creation documentation link
- Encourage sharing updated AMI with WebArena community
- Helps streamline setup for future users
Co-authored-by: openhands <openhands@all-hands.dev>
- Add instructions to configure frontend to use existing AWS tile server (18.208.187.221)
- This is required even if users don't set up their own backend
- Fixes map functionality by pointing to currently running tile server
Co-authored-by: openhands <openhands@all-hands.dev>
- Add link to AWS EC2 Launch Tutorial for launching instances
- Add link to AWS User Data Documentation for cloud-init usage
- Helps users learn how to launch instances and configure user data
Co-authored-by: openhands <openhands@all-hands.dev>
- Include 18.208.187.221 as example IP in deployment instructions
- Helps users understand what to replace <BACKEND_IP> with
Co-authored-by: openhands <openhands@all-hands.dev>
