chore(railway): add sandbox-agent preview deployment#4787
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Context
Railway previews need the sandbox-agent service to run beside API/services and receive the same Daytona credentials used by the agent runtime. Without a Railway slice, the POC can be tested locally but not in preview environments.
This PR is stacked on #4786 and should be reviewed with the existing agent-workflows POC PRs (#4771, #4772, #4776, #4778, #4779).
Changes
Adds the Railway deploy workflow wiring for the sandbox-agent Daytona key, adds a Railway service Dockerfile wrapper for
agenta-sandbox-agent, and updates the Railway scripts so configure, deploy, bootstrap, and preview-env resolution include the runner service. The Railway self-host guide now documents the sandbox-agent service in the Railway deployment path.Tests / notes
What to QA
sandbox-agentservice should be created and receiveSANDBOX_AGENT_DAYTONA_API_KEY.