Repository navigation
chore: deploy as a Vercel Daemon - #66
Merged
Merged
Conversation
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
marked this pull request as ready for review
November 10, 2026 16:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Run the bot on Vercel as a Daemon (beta), built from the existing
Dockerfile.vercel.jsondeclares a singlecodercorddaemon (1 instance,iad1, 1Gi). Keep it at 1 instance, or every Gateway event fires twice.SIGTERM, so the old and new instances do not overlap during a deploy.robots.txttopublic/(gitignored).Secrets go in the Vercel project's environment variables (Production scope). Daemons only run on production deployments.
Agent assisted (Xum, Claude).