WebsiteBench / tasks /linkedin /solution /site /implementation /clone /deploy /README-public-deployment.md
AgPerry's picture
Add files using upload-large-folder tool
9d4a3b0 verified
|
Raw History Blame Contribute Delete
889 Bytes

Public deployment integration

This project is prepared as the LinkedIn WebsiteBench public deployment candidate.

Status:

  • Dockerfile.public runs the Next standalone server as a non-root user on port 10000.
  • /healthz, /public-register, /static/auth-verification.js, the public OTP APIs, and WebsiteBench bench probes are present.
  • Public OTP uses the WebsiteBench public clone auth contract with Redis/Resend routed by the public deployment workflow.
  • Provider secrets must stay in GitHub/WebsiteBench configuration only: REDIS_REST_URL, REDIS_REST_TOKEN, RESEND_API_KEY, and RESEND_FROM_EMAIL.
  • Stripe remains workflow-pending for public deployment. The deployment candidate does not require card payment for the core registration path.
  • Full public OTP account-creation evidence is pending until the GitHub workflow runs with authorized mail-domain evidence.