Repository navigation
AD2: admin-dashboard becomes an Orun baseline - #3
Merged
Merged
Conversation
postgres-drizzle-starter's machinery on this tree, in the turso v8 shape: blueprint.yaml (the console card: Cloudflare and Supabase, five brokered keys, the subdomain read from the connection, no domain asked, GitHub sign-in the owner's to connect afterwards) and repo-blueprint.yaml (one landing, 01-product, then the record, 02-docs; task set-up in the background, landings checked in the box, a 5 s watch, one secrets reconcile). .baseline/ (identity, the product's README with Connecting GitHub sign-in and Deploy by hand, task contracts), the rename engine (Vercel's page for the template, which spells this slug, masked), the bootstrap helpers, the deployment-record renderer probing /, /api/health and /api/auth/providers, the phase pages, the context pack, and the baseline's tests: manifest, phases, coverage, rebrand, retouch, bootstrap-defer, generated component docs, the leak gate, the offline bootstrap with the product's own plan (supabase, cloudflare-hyperdrive, db-migrate, web, enforced; the GitHub refs optional), and the end-to-end tier that migrates the stage database through a stand-in Supabase Management API over a real Postgres, then serves the built Worker over it: eight concurrent first requests through the proxy, both pages and the search over the seeded products, the login page with GitHub not connected, a session under the database's key read and another refused, a product written behind its back found, and the Data API's roles shut out of the table and the key. The contract tiers, the leak gate and placement pass locally on orun v2.89.0; the e2e tier runs on Baseline CI (it needs a PostgreSQL server). Co-Authored-By: Claude <noreply@anthropic.com> Orun-Task: AD-3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
postgres-drizzle-starter's machinery on this tree, in the turso v8 shape: blueprint.yaml (the console card: Cloudflare and Supabase, five brokered keys, the subdomain read from the connection, no domain asked, GitHub sign-in the owner's to connect afterwards) and repo-blueprint.yaml (one landing, 01-product, then the record, 02-docs; task set-up in the background, landings checked in the box, a 5 s watch, one secrets reconcile). .baseline/ (identity, the product's README with Connecting GitHub sign-in and Deploy by hand, task contracts), the rename engine (Vercel's page for the template, which spells this slug, masked), the bootstrap helpers, the deployment-record renderer probing /, /api/health and /api/auth/providers, the phase pages, the context pack, and the baseline's tests: manifest, phases, coverage, rebrand, retouch, bootstrap-defer, generated component docs, the leak gate, the offline bootstrap with the product's own plan (supabase, cloudflare-hyperdrive, db-migrate, web, enforced; the GitHub refs optional), and the end-to-end tier that migrates the stage database through a stand-in Supabase Management API over a real Postgres, then serves the built Worker over it: eight concurrent first requests through the proxy, both pages and the search over the seeded products, the login page with GitHub not connected, a session under the database's key read and another refused, a product written behind its back found, and the Data API's roles shut out of the table and the key. The contract tiers, the leak gate and placement pass locally on orun v2.89.0; the e2e tier runs on Baseline CI (it needs a PostgreSQL server).
🤖 Generated with Claude Code