DocsKnowledge base
Launch Checklist
A focused checklist for publishing Mementropy while keeping the standalone Admin application private.
Public application
Section titled “Public application”-
siteis set tohttps://mementropy.comin the rootastro.config.mjs -
npm run checkandnpm run buildsucceed from the repository root - The public build contains no
dist/admin/tree or internal/adminlinks - The root
wrangler.jsonctargets the public Pages project and./dist - Cloudflare Pages publishes the latest public commit successfully
-
mementropy.comserves 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
Standalone Admin application
Section titled “Standalone Admin application”-
siteis set tohttps://admin.mementropy.cominapps/admin/astro.config.mjs -
npm --prefix apps/admin run checkandnpm --prefix apps/admin run buildsucceed - 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.jsonctargetsmementropy-adminand./dist -
admin.mementropy.comrequires Cloudflare Access when logged out -
mementropy-admin.pages.devrequires Cloudflare Access when logged out - Current hash and branch previews under
*.mementropy-admin.pages.devrequire 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