mg-railway-deploy-all

To deploy all ModelGuide services, use the command 'mg-railway-deploy-all deploy all --project <project> --environment <env>'. This automates parallel deployment of the API, UI, and LB services from their specific subdirectories to your Railway environment.

No, you cannot run database migrations during the ModelGuide deployment process. This Skill explicitly excludes database migrations, so you must run any required database schema updates separately before or after deploying your services.

Yes, you need the Railway MCP tools installed to automate ModelGuide deployments. The Skill requires the railway-mcp dependency to handle linking to the correct Railway project and environment, and to execute the parallel service deployments.

Preflight checks ensure the Railway link resolves to the repository root and verify the link is correct before deploying. This prevents deployment errors by confirming the project and environment configuration is accurate prior to starting the parallel service deployment.

Automated Railway deployment maps each service to its specific subdirectory for accurate deployment. The API, UI, and LB services are deployed in parallel from their respective directories, and the system checks deployment logs to monitor the process.

Manual Railway deployments often fail due to incorrect project linking or environment misconfiguration. Using an automated deployment Skill performs preflight checks to ensure the Railway link resolves correctly to the repo root before deploying the API, UI, and LB services.