# Infrastructure Working Group Discussions
Summaries of infrastructure-related discussions
## 2025 January 20 Infrastructure Discussion
> **Model Used:** ________
> **Prompt:** _____________
> **Link to Source:** Discord
> **Summary:** Discussion between core development team and Numinia team reviewing infrastructure settings and needs
### Core Infrastructure (AWS)
- Using ECS (Elastic Container Service) as container orchestrator
- EFS for persistent volume storage
- S3 storing PM2 configuration files
- AWS Secrets Manager handling environment variables
- Load balancers routing traffic to different ports (3000, 3001, etc.)
- Terraform managing infrastructure as code
### Current Implementation
- Each subdomain points to specific ports via load balancer
- Load balancer listens on 443, redirects to specific ports
- Multiple worlds can run on single instance
- Worlds currently run persistently (no auto-scaling)
- Environment config sourced from:
1. ecosystem.config.json for storage/general parameters
2. AWS Secrets Manager for sensitive data
### Development Workflow
- Currently building directly on server due to EFS connection limitations
- Working with Hyperfy main branch + custom modifications
- Plans to implement staging environments
- Future goal: local development with production deployments
- Some worlds will need live building capability for roleplay purposes
### Challenges & Future Improvements
- Auto-scaling worlds based on user presence
- Optimizing instance size vs number of worlds per instance
- Making infrastructure code more generic
- Implementing proper staging environments
- Improving volume mounting configuration
- Need for VPN/bastion for local EFS connections
### Collaboration Points
- Interest in coordinating with other platform builders
- Avoiding duplicate infrastructure work
- Maintaining alignment with main Hyperfy codebase
- Suggestion for infrastructure/platforms Discord channel
- Code cleanup and documentation in progress
- Pull request planned for mounting point modifications
### Team Focus
- Primary focus on roleplay gameplay development
- Infrastructure development secondary but necessary
- Interest in contributing to core Hyperfy improvements
- Emphasis on maintaining single unified engine
## 2025 Jan 16 infrastructure Working Group
> **Model Used:** Maximus
> **Prompt:** Summarize points and takeaways
> **Link to Source:** Discord
> **Summary:** Discussion between core development team and Numinia team reviewing infrastructure settings and needs
### Summary
* A group of folks happened to strike up a conversation with the Numinia team PabloFM + DevStarlight
* Numinia sees huge changes in the way enterprise workers will be interacting and completing work through immersive experiences
* A key challenge is educating the clients on the tech and have decision makers understand how to make best use of the technology
* Events remain a popular use case for immersive worlds
* Numinia's vision is to provide broadly accessible 3d immersive experiences (using any device globally)
* Currently the team is tracking performance and analytics of worlds to be able to correctly price the use of the servers to support their client services
### Takeaways
* The teamn touched upon a few main takeways to support infrastructure builders:
1. Connect with other infrastructure-enterprise service providers
2. Support and coordinate with community members to encourage quality/automation such as running test scripts to catch breaking error
{%hackmd Syq4xkPwkg %}