ci: add railway deployment workflow

[master-kanor]

Summary

Changes

Type

• Bug fix
• New feature
• Documentation
• Refactoring
• Performance improvement
• Other (describe below)

Testing

• Added/updated unit tests
• Tested manually (describe steps below)
• No tests needed (explain why)

Checklist

• My code follows the existing code style
• I have tested my changes locally
• I have updated documentation (if applicable)
• All existing tests pass (npm test)
• This PR has a descriptive title

Related Issues

[github-actions]

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 can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[github-actions]

👋 Welcome, @master-kanor, and thanks for opening your first PR on AnythingMCP!

A few quick pointers:

• Make sure CI is green before requesting review (Backend, Frontend, Playwright, CodeQL, Trivy).
• If this is a new adapter, the parametrised catalog.spec.ts test will validate it automatically.
• Sign off your commits if you can — it's not blocking, just nice to have.

Someone from the core team will look at this within ~48h. If you don't hear back, please ping us in Discussions / Q&A.

⭐ While you wait — if you find AnythingMCP useful, a star helps others discover it.

[keysersoft]

Hi @master-kanor, thanks for this — automated Railway deploys are a genuinely useful addition, and I’d like to take them.

There’s one thing to sort out first: this branch also carries chore: rename project from anythingmcp to open-hide, which rebrands the upstream project to your fork. I’m guessing that came along by accident from your fork’s working branch. A few of those lines would be breaking for everyone if merged — the compose files would pull hillstreetph/open-hide:latest instead of the official image, railway.json would repoint our deploy button at your fork, and the DATABASE_URL database rename would break every existing install (since POSTGRES_DB only applies on first init).

Could you open a fresh PR from a clean branch off main containing only:

.github/workflows/deploy-railway.yml
the CI/CD section in docs/deployment.md (without the fork-specific project id / repo name)
Two small asks on the workflow itself: please make it workflow_dispatch-only (or guard it with if: github.repository == 'HelpCode-ai/anythingmcp') — as written, on: push would run on every merge to main and fail, since upstream has no RAILWAY_TOKEN. And actions/checkout@v6 to match the rest of our workflows.

Also, the CLA check needs a one-line comment on the PR to pass:
I have read the CLA Document and I hereby sign the CLA

To be clear, your fork is entirely welcome to carry its own name — AGPL-3.0, and you kept the license and attribution, which I appreciate. It’s just the upstream repo that needs to stay AnythingMCP. Ping me when the new PR is up and I’ll review it quickly.