Repository navigation
Add a Self-Hosting guide, including Bring Your Own Detector - #100
Conversation
✅ Deploy Preview for peaceful-pothos-9e62ce ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
17ac780 to
fa8a66f
Compare
|
No updates since Nothing is lost — Converting to draft disables auto-merge, so PRs with auto-merge enabled are excluded from this entirely. |
|
No updates since Nothing is lost — Converting to draft disables auto-merge, so PRs with auto-merge enabled are excluded from this entirely. |
|
No updates since Nothing is lost — Converting to draft disables auto-merge, so PRs with auto-merge enabled are excluded from this entirely. |
We claim on the marketing site that Procaptcha can be self-hosted but had no instructions to back it up. The only ones that existed were in a GitHub Discussion comment describing a fork-and-edit-TypeScript workflow. A public comparison article picked this up and called the self-hosting story a joke, which was fair. Adds a Self-Hosting section documenting the real short path: four containers using the published prosopo/provider image and the provider.Caddyfile we run in production, then a site key registered with an explicit --captcha_type. A concrete captcha type short-circuits the frictionless scoring path, so no detector is needed, and neither pow nor puzzle needs an image dataset. The image type is covered too, since it works given a dataset you build and host. The page is explicit about where self-hosting stops. Serving challenges is one half of bot protection; the ML scoring, automatic blocking, access rules and analytics that Professional and Enterprise provide are the other half, and none of it runs on a self-hosted node. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… Bring Your Own Detector Matches SELF_HOSTING.md as of prosopo/captcha#3585: pnpm commands, the widget loaded with type="module" (the chunked bundle fails without it), the image version taken from the checkout, and a Bring Your Own Detector section using the BotD example. Drops "bring your own detector support is planned". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fa8a66f to
5ed8721
Compare
forgetso
changed the title
What changed
Adds a Self-Hosting page to the docs, at docs.prosopo.io/en/self-hosting/.
It explains how to run Procaptcha on your own servers using the public
prosopo/providerimage: generate an.env, start the shipped compose file, register a site key, build the widget, and verify tokens. It also covers:It matches
SELF_HOSTING.mdin the captcha repo, and that file already links here (the link is a 404 until this merges).Effect
The marketing pages say Procaptcha can be self-hosted. Until now, the only instructions were an out-of-date GitHub Discussion comment that told people to fork the repo and edit TypeScript. This page replaces that comment, and the discussion will point here.
Test coverage
Docs only. The site builds and every anchor on the page resolves. Every command on the page was run against a real stack: the original flow in September, and the detector flow against a provider built from prosopo/captcha#3585.
🤖 Generated with Claude Code