Search & explore

• Level L03
• T06
• 20 min read

Take the Base44 app from T06-L02 · Build a Small Shared Tool From a Prompt, and Test It With a Colleague to where colleagues can depend on it: two roles the data enforces, clear empty and error screens, a test copy with known answers, an operating note with a maintainer and deputy, and a line where IT takes over.

• Level L05
• T06
• 18 min read

Operate a team app that many people rely on, for years: every change through a staging copy, a rollback you have practised, outside checks on sign-in, backups and certificates, a yearly plan for updates, licences and costs, a quarterly access review, and a deputy who can release, roll back and restore without you.

Matching textT06-L05 · Build apps · Level 5 Operator · 19-minute read, plus 6 hours of doing over a month Run the App Others Depend On, and Hand It Over Friday afternoon, three hours without

• Level L04
• T06
• 22 min read

Move a team app's data out of the app builder into a self-hosted Supabase, the open-source PostgreSQL platform, that your IT runs. Enforce who sees which rows with row-level security, give every person, program and assistant its own narrow login, back up off the server, and restore into an empty database.

Matching textT06-L04 · Build apps · Level 4 Integrator · 20-minute read, plus about 6 hours of doing over two weeks Put Your Team App on the Organisation's Own Database, and Prove You Can Restore

• youtube
• 13 min video

Iteratively prompt, inspect generated data and test a published prototype. Sponsored; not proof of private invitations, complete persistence or secure authorisation.

Matching textT06-L02: Follow a sponsored Base44 prototype build through follow-up prompts, data inspection and a second-account check after publication. Use the book for private invitations, persistence tests…

• youtube

Implement database row-level access policies. Historical interface; RLS alone not field restrictions, hosting security or restoration.

Matching textT06-L04: See how Supabase row-level policies restrict records to the right user, with a two-account example. The interface is historical; use the book for field restrictions, self-hosting and…

• youtube

Promote the same tested artifact through staging and production without rebuilding. 2016 TeamCity/Octopus/.NET, not Dokploy; no database rollback guarantee.

Matching textT06-L05: Study staging and production promotion at 37:20–41:15 in JetBrains' official recording. This 2016 TeamCity/Octopus example supports staged release planning, not current Dokploy instructions…

One-page diagram to use with T06-L05, "Run the App Others Depend On, and Hand It Over", and 1 more book.

One-page diagram to use with T06-L02, "Build a Small Shared Tool From a Prompt, and Test It With a Colleague".