syntaqxEmail sign-up has a Cloudflare Turnstile check, when it is set up. With TURNSTILE_SITE_KEY (a var in apps/web/wrangler.jsonc: the widget's public site key) and the TURNSTILE_SECRET secret both set, the sign-up form draws Turnstile's widget above its button and the server checks its answer with Cloudflare's siteverify before identity is asked; a missing or refused answer gets a plain error. With either unset nothing changes, so an installation of its own and local development sign up without it; when Cloudflare cannot be reached the sign-up goes ahead, the rate limit and email confirmation still in its way. The page's policy allows Turnstile's script and frame from challenges.cloudflare.com, and nothing else is framed. The self-hosted compose file and configs pass both keys through. The accounts and self-hosting guides say so.f68a2ddHistory
- ..
- 0001_init.sql
- 0002_lifecycle.sql
- 0003_repo_settings.sql
- 0004_up_to_date.sql
- 0005_assignees.sql
- 0006_merge_rules.sql
- 0007_timeline.sql
- 0008_plans.sql
- 0009_lifecycle_snapshot.sql
- 0010_merge_queue.sql
- 0011_agent_messages.sql
- 0012_exchanges.sql
- 0013_commit_statuses.sql
- 0014_mergeability.sql
- 0015_agent_runs_and_memory.sql
- 0016_by_author.sql
- 0017_agent_mentions.sql
- 0018_guardrails.sql
- 0019_memory_capture.sql
- 0020_agent_waits.sql
- 0021_confidence.sql
- 0022_required_checks.sql
- 0023_read_paths.sql
- 0024_g1t_name.sql
- 0025_requested_by.sql
- 0026_code_owners.sql
- 0027_labels_milestones_bases.sql
- 0028_rulesets.sql
- 0029_commit_checks.sql
- 0030_comment_edits.sql
- 0031_mention_revisions.sql
- 0032_contributions.sql
- 0033_agent_comments.sql