Skip to content
MementropyKnowledge
DocsKnowledge base

Launch Checklist

A focused checklist for publishing Mementropy while keeping the standalone Admin application private.

  • site is set to https://mementropy.com in the root astro.config.mjs
  • npm run check and npm run build succeed from the repository root
  • The public build contains no dist/admin/ tree or internal /admin links
  • The root wrangler.jsonc targets the public Pages project and ./dist
  • Cloudflare Pages publishes the latest public commit successfully
  • mementropy.com serves HTTPS, search works, and all four public lanes are available without authentication
  • Legacy /admin, /admin/recipes/, and /admin/planning/ URLs redirect to the standalone Admin host
  • site is set to https://admin.mementropy.com in apps/admin/astro.config.mjs
  • npm --prefix apps/admin run check and npm --prefix apps/admin run build succeed
  • The Admin build contains /, /recipes/, and /planning/, but no Pagefind index
  • The Admin build emits Disallow: /, no-index, and private/no-store controls
  • apps/admin/wrangler.jsonc targets mementropy-admin and ./dist
  • admin.mementropy.com requires Cloudflare Access when logged out
  • mementropy-admin.pages.dev requires Cloudflare Access when logged out
  • Current hash and branch previews under *.mementropy-admin.pages.dev require Cloudflare Access
  • All three Admin applications allow only exact approved email addresses
  • A disallowed account is denied and an approved account reaches every Admin route
  • The Access session duration is appropriate for the private workspace