operator guides
Deploy & wire-up
Step-by-step flows — templates on dev.binarykernel.xyz, live on www.binarykernel.xyz, plus subdomains and Hugging Face Spaces.
Dev → live workflow
- Build and preview templates on dev.binarykernel.xyz.
- When pages are ready, promote the same project to www.binarykernel.xyz.
- Keep dev for staging — never push untested templates straight to production.
First landing deploy (live)
- Push binarykernel-site to GitHub and connect in Vercel.
- Add www.binarykernel.xyz as the primary domain (canonical).
- Add binarykernel.xyz with a 308 redirect → www (Vercel CDN recommendation).
- Set NEXT_PUBLIC_* env vars for Jira, Slack, and HF URLs when ready.
Dev & templates (dev.binarykernel.xyz)
- Add dev.binarykernel.xyz in Vercel → Domains on the staging project.
- In DNS: CNAME dev → cname.vercel-dns.com.
- Scaffold templates locally, deploy to dev, review animations and copy.
- Promote to www.binarykernel.xyz only after sign-off.
Wire a subdomain
- Add CNAME in DNS: e.g. hermes.binarykernel.xyz → your target.
- In Vercel, add the subdomain only on the project that serves that surface.
- Match the subdomain to the HF Space or app listed in /spaces.
Observability (Sentry)
- Connect GitHub at binarykernel.sentry.io → Settings → Integrations → SCM.
- Set NEXT_PUBLIC_SENTRY_DSN, SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT in Vercel.
- staging tag on dev.binarykernel.xyz · production on www.binarykernel.xyz.
Hermes on Hugging Face
- Read binarydoc-hermes-space README for secrets list.
- Duplicate HermesFace or use BinaryKernel Hermes Space template.
- Enable HF dataset sync for persistent memory across restarts.
Domain map
- apexbinarykernel.xyz
- wwwwww.binarykernel.xyz
- devdev.binarykernel.xyz
- hermeshermes.binarykernel.xyz
- hfhf.binarykernel.xyz
- vercelvercel.binarykernel.xyz
- slackslack.binarykernel.xyz
- tanstacktanstack.binarykernel.xyz
- figmafigma.binarykernel.xyz
- gitgit.binarykernel.xyz
- hubhub.binarykernel.xyz
- docsdocs.binarykernel.xyz
- spacesspaces.binarykernel.xyz