Skip to content

chore: deploy as a Vercel Daemon - #66

Merged
phorcys420 merged 4 commits into
mainfrom
phorcys/vercel-daemon
Nov 10, 2026
Merged

phorcys420 merged 4 commits into
mainfrom
phorcys/vercel-daemon

Conversation

@phorcys420

Copy link
Copy Markdown
Member

Run the bot on Vercel as a Daemon (beta), built from the existing Dockerfile.

  • vercel.json declares a single codercord daemon (1 instance, iad1, 1Gi). Keep it at 1 instance, or every Gateway event fires twice.
  • The bot now disconnects from the Gateway on SIGTERM, so the old and new instances do not overlap during a deploy.
  • Vercel needs a non-empty output directory that is not the daemon root, so the build writes a robots.txt to public/ (gitignored).

Secrets go in the Vercel project's environment variables (Production scope). Daemons only run on production deployments.


Agent assisted (Xum, Claude).

Add vercel.json to run the existing Dockerfile as a single-instance Vercel Daemon, and disconnect from the Gateway on SIGTERM so the old and new instances do not overlap during a deploy.
Vercel publishes the repo root as static files when no output directory is set, which conflicts with the daemon root. Point it to an empty public/ directory instead.
Vercel refuses an empty output directory. Generate a robots.txt that disallows all crawlers, so the directory has content.
@phorcys420
phorcys420 marked this pull request as ready for review November 10, 2026 16:02
@phorcys420
phorcys420 merged commit 03afeae into main Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant