enhancement: Deploy to Railway/Vercel/Netlify buttons

[lefarcen]

Feature Request

Add one-click deploy buttons for popular PaaS platforms.

Platforms

Railway

[![Deploy on Railway](https://railway.app/button.svg)](https://railway.app/new/template/open-design)

Vercel

• vercel.json configuration
• Environment variables setup
• Deploy button

Netlify

• netlify.toml configuration
• Build settings
• Deploy button

Render

• render.yaml configuration
• Auto-deploy from GitHub

Benefits

• Zero-config deployment
• Free tier available
• Perfect for demos/prototypes

Implementation

Create platform-specific config files and update README with deploy buttons.

Related Issues

Depends on: #1019 (Docker)

Priority

P2 - Low barrier to entry, great for community growth.

---

Reported by: @黄巍 via Looper Bot

[lefarcen]

This looks like a good first issue for someone new to the project.

If you'd like to work on it, comment /claim below. The first /claim after the latest release gets it. Any comment, linked PR, or progress note keeps the claim active.

[lefarcen]

Quick investigation note: #1019 is not a blocker — Docker infrastructure already landed in #65, and vercel.json exists from #167.

Current state:

• ✅ Docker deployment ready (deploy/ directory)
• ✅ Vercel config exists
• ❌ Missing: netlify.toml, render.yaml, Railway config
• ❌ Missing: README deploy button section

Implementation scope estimate:

• Render/Railway: Can build on existing Docker image
• Vercel/Netlify: Static web layer (may need daemon connectivity docs)
• Config files needed for each platform
• Verification deploy per platform before claiming zero-config

This is a good medium-complexity first issue. Whoever claims should verify at least one successful deployment per button before opening the PR. 🚀

[Maou3434]

/claim

I’ve reproduced this issue locally and already have a working fix for the Netlify deployment flow.
Currently extending/testing the fix for Render and Railway before opening the PR.
Vercel deployment appears to already be handled.

[lefarcen]

Claimed by @Maou3434. Thanks for picking this up! 🎉

Quick question to time check-ins right — roughly how long do you think this will take?

• A few hours / today
• 1-3 days
• ~ 1 week
• Longer / unsure

Reply with whatever fits. If you don't reply, I'll default to checking in every ~12h. Either way, any comment, linked PR, or progress note keeps the claim active.

[Maou3434]

1-3 days

[Maou3434]

Fixing some issues with being unable to ping render to verify public link
will do some fixes and keep you updated

[Maou3434]

The core fix is already implemented and working locally. I'm currently wrapping up validation, making a few Railway-specific adjustments, and cleaning up the codebase before submitting the PR. I'll finish the remaining work tomorrow morning after getting some rest.

[lefarcen]

Hey @Maou3434, your implementation is up in PR #3388 now.

It covers the core scope from this issue by wiring native Netlify, Render, and Railway deployment paths into the app, including the provider-specific credential flow and the Netlify GitHub deploy-key/linking fix that came up during your validation notes here. Keeping this issue open until the PR lands so the request and implementation stay tied together.

[Maou3434]

Hi @leilei926524-tech, just a heads-up that this issue is already being worked on and the implementation is currently under review in PR #3388. Since the scope from the issue is already covered there, it would probably be best not to advertise it as available work for others to pick up. Keeping discussion and progress consolidated in the existing PR should help avoid duplicate effort. Thanks!