ci: socket realtime image for hosting

[adiologydev]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Note: The image is highly unoptimized because it's all packaged within the same app in our mono-repo, this will gradually become a lot more lightweight once we properly utilise the mono-repo.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Security enhancement
• Performance improvement
• Code refactoring (no functional changes)

How Has This Been Tested?

Locally built and ran.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

Additional Information:

Any additional information, configuration or data that might be necessary to reproduce the issue or use the feature.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 27, 2025 3:59pm
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 27, 2025 3:59pm

[greptile-apps]

PR Summary

Added new realtime Socket.IO server infrastructure with Docker configuration for hosting. This introduces a critical service component for real-time functionality across the platform.

• Added new matrix entry in .github/workflows/build.yml to build ghcr.io/simstudioai/realtime image
• Created docker/realtime.Dockerfile with Bun runtime configuration for Socket.IO server on port 3002
• Modified docker-compose.prod.yml to integrate realtime service with proper health checks and dependencies
• Note: Current implementation bundles entire app due to mono-repo structure, pending future optimization

_{4 files reviewed, 2 comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Second bun install is redundant since deps were already copied. Consider removing this step

[adiologydev]

Good catch

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to 841934c.

Security Overview

• 🔎 Scanned files: 10 changed file(s)

Detected Code Changes

Change Type	Relevant files
Configuration changes	► .devcontainer/Dockerfile     Add new port exposure ► docker-compose.local.yml     Add realtime server configuration ► docker-compose.prod.yml     Add realtime server configuration ► .github/workflows/build.yml     Add realtime Dockerfile to build matrix
Enhancement	► docker/realtime.Dockerfile     Add new Dockerfile for realtime server ► package.json     Add new development scripts ► apps/sim/package.json     Update development scripts ► packages/cli/src/index.ts     Add realtime server container support ► README.md     Update development setup instructions

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[waleedlatif1]

@adiologydev can we add any info to the README to let users know how to run the pkg. we also need to think about how we can modify the root package.json build command maybe like dev:full to run the socket server by default. not sure if there are best practices in place for sockets/external servers and how they should be ran

[adiologydev]

@adiologydev can we add any info to the README to let users know how to run the pkg. we also need to think about how we can modify the root package.json build command maybe like dev:full to run the socket server by default. not sure if there are best practices in place for sockets/external servers and how they should be ran

Sure, will add additional information about it in the readme.

It's not advisable in production to use concurrently. Also the way we build the app (standalone), we can't really package anything else together in that image.