docs(deploy): add Railway Dockerfile configs to fix pnpm catalog buil…

[gixagency]

…d failures

Railway's default Nixpacks builder falls back to npm install for the web/admin/space/live services, which chokes on pnpm's catalog: protocol used across package.json. Add per-service railway.json configs that point Railway at the existing production Dockerfiles (same ones used by docker-compose.yml) plus setup docs covering root directory, build args, CORS, and ports.

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

• New Features
  • Added Railway deployment configs for the web, admin, space, live, and API services.
  • Enabled Dockerfile-based builds and automatic retry-on-failure settings for deployments.
• Documentation
  • Expanded Railway setup instructions with service-specific steps, port settings, and required environment variables.
  • Clarified how to complete initial deploys and configure service domains and allowed origins.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4fa7cc48-dded-492a-86cd-8050dba1c777

📥 Commits

Reviewing files that changed from the base of the PR and between 24fad36 and d628cb4.

📒 Files selected for processing (6)

• deployments/railway/community/README.md
• deployments/railway/community/railway.admin.json
• deployments/railway/community/railway.api.json
• deployments/railway/community/railway.live.json
• deployments/railway/community/railway.space.json
• deployments/railway/community/railway.web.json

---

📝 Walkthrough

Walkthrough

Adds Railway deployment configuration JSON files for the admin, api, live, space, and web services, each specifying Dockerfile-based builds and restart policies. Updates the community README with instructions for switching from Nixpacks to Dockerfile builds and configuring services on Railway.

Changes

Railway Deployment Configuration

Layer / File(s)	Summary
Per-service Dockerfile build configs deployments/railway/community/railway.admin.json, deployments/railway/community/railway.api.json, deployments/railway/community/railway.live.json, deployments/railway/community/railway.space.json, deployments/railway/community/railway.web.json	Each JSON declares the Railway schema, configures a Dockerfile-based build pointing at the corresponding app Dockerfile, and sets deploy restart policy to ON_FAILURE with max 3 retries.
Deployment guidance documentation deployments/railway/community/README.md	Documents the pnpm catalog: / Nixpacks build failure, instructs switching services to the Dockerfile-based config-as-code files, adds dashboard setup steps (root directory, builder, port), build-time VITE_*_BASE_URL variables, initial deploy/redeploy workflow, CORS_ALLOWED_ORIGINS for api, and PORT=3000 requirements for space/live.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Related PRs: None mentioned in the diff.

Suggested labels: documentation, deployment

Suggested reviewers: None specified in the provided diff.

🐰 hops through configs, tidy and small, Dockerfiles lined up, ready to call, README whispers why npm failed, Railway's new path, cleanly detailed, Carrots and JSON, deployed for all.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is mostly template placeholders and lacks the required detailed sections and test notes.	Fill in the Description, Type of Change, Test Scenarios, and References sections, and add screenshots if applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: Railway Dockerfile configs to fix pnpm catalog build failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}