WebsiteBench / tasks /linkedin /solution /site /implementation /clone /deploy /README-public-deployment.md
|
Download tasks/linkedin/solution/site/implementation/clone/deploy/README-public-deployment.md from TIGER-Lab/WebsiteBench: direct link, hf CLI and curl.
- Browser
- Download file 889 Bytes
-
https://huggingface.co/datasets/TIGER-Lab/WebsiteBench/resolve/main/tasks/linkedin/solution/site/implementation/clone/deploy/README-public-deployment.md
- Command line
-
hf download hf://datasets/TIGER-Lab/WebsiteBench/tasks/linkedin/solution/site/implementation/clone/deploy/README-public-deployment.md
-
curl -L -o README-public-deployment.md https://huggingface.co/datasets/TIGER-Lab/WebsiteBench/resolve/main/tasks/linkedin/solution/site/implementation/clone/deploy/README-public-deployment.md
889 Bytes
Public deployment integration
This project is prepared as the LinkedIn WebsiteBench public deployment candidate.
Status:
Dockerfile.publicruns the Next standalone server as a non-root user on port10000./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, andRESEND_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.