supython 0.1.1__tar.gz → 0.1.2__tar.gz

{supython-0.1.1 → supython-0.1.2}/CHANGELOG.md

@@ -31,7 +31,7 @@ Each entry links the relevant `PROJECT.md` section and decision-log row
 
 ---
 
-## [0.1.0] — 2026-05-08
+## [0.1.0] — 2026-05-09
 
 The first public release. Everything currently on `main` collapses
 into this single ZeroVer entry — auth, storage, functions, realtime,
@@ -200,5 +200,5 @@ v0.1–v0.7 plus a v1.1.x admin track; see §19 decision log
 
 ---
 
-[Unreleased]: https://github.com/Tkeby/supython/compare/v0.1.0...HEAD
+
 [0.1.0]: https://github.com/Tkeby/supython/releases/tag/v0.1.0

{supython-0.1.1 → supython-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: supython
-Version: 0.1.1
+Version: 0.1.2
 Summary: A lightweight Postgres-first BaaS framework for Python
 Project-URL: Homepage, https://github.com/Tkeby/supython
 Project-URL: Repository, https://github.com/Tkeby/supython
@@ -58,10 +58,10 @@ Description-Content-Type: text/markdown
 
 # supython
 
-> A lightweight, Postgres-first BaaS framework for Python. **v0.1.0 release**
+> A lightweight, Postgres-first BaaS framework for Python. **v0.1.2 release**
 
-supython is the inverse of Django: **the database owns the schema, Python owns
-the things SQL is bad at**. It leans on [PostgREST](https://postgrest.org)
+**the database owns the schema, Python owns the things SQL is bad at**. 
+It leans on [PostgREST](https://postgrest.org)
 for auto-generated REST APIs and on Postgres' own RLS for authorization,
 while a small FastAPI service in Python handles auth, JWT issuance, realtime,
 storage, functions, workers, and an optional admin control plane.
@@ -69,7 +69,7 @@ storage, functions, workers, and an optional admin control plane.
 supython is for a specific person with a specific problem:
 > A developer who wants to build a CRUD-heavy web app (most apps are), who thinks in SQL, who wants Postgres to own authorization, and who wants auth + storage + custom logic without assembling the integration themselves.
 
-Shipped [v0.1.0]:
+Shipped [v0.1.2]:
 
 **Core platform**
 - **Email/password auth** — signup, login, refresh-token rotation with **reuse detection**
@@ -88,7 +88,7 @@ Shipped [v0.1.0]:
 
 **Realtime**
 - **WebSocket Realtime** — `postgres_changes`, `broadcast`, `presence` with per-subscriber RLS filtering
-- **Phoenix Channels wire format** — unmodified `supabase-js` / `supabase-py` SDKs connect
+- **Phoenix Channels wire format** 
 - **Generic trigger** — `realtime.enable('public.todos')` opts any table in
 - **Two-browser chat demo** — `examples/chat.html` (zero build step)
 
@@ -106,7 +106,7 @@ Shipped [v0.1.0]:
 - **Secret rotation** — JWT keys, symmetric secrets, Postgres passwords; all with zero-downtime runbooks
 - **Multi-arch Docker image** — `linux/amd64` + `linux/arm64`, non-root user, `tini` PID 1, ~64 MB
 
-**Admin control plane** (shipped in v0.1.0)
+**Admin control plane** (shipped in v0.1.2)
 - **Vue 3 + Vite SPA** at `/admin` — no runtime Node deps; pre-built static bundle in the wheel
 - **Database surface** — schema browser, table data with role switcher, SQL workspace (read-only default + write toggle), RLS policy editor with dry-run, migrations panel
 - **Auth surface** — user search, ban/unban/force-logout, refresh-token inspector, audit log, email template editing
@@ -159,7 +159,7 @@ cp .env.example .env
 # the value PostgREST will use (docker-compose.yml injects it via env).
 #
 # The scaffold creates:
-#   manage.py         — Django-style CLI entrypoint (sets SUPYTHON_SETTINGS_MODULE)
+#   manage.py         — Optional CLI entrypoint (sets SUPYTHON_SETTINGS_MODULE)
 #   myapp/settings.py — declare EXTENSIONS, EXTRA_ROUTERS, EXTRA_MIDDLEWARE
 #   myapp/jobs.py     — example @job seed (register your background jobs here)
 #   myapp/hooks.py    — example @on("signup") seed (lifecycle hooks)
@@ -219,8 +219,7 @@ including filtering, sorting, refresh, and isolation between users.
 ## Realtime quickstart
 
 supython ships a WebSocket engine that speaks the **Phoenix Channels 5-tuple
-protocol** used by every official Supabase SDK.  Unmodified `supabase-js` and
-`supabase-py` clients connect without any shim.
+protocol**.
 
 ### 1. Opt a table into realtime
 
@@ -444,7 +443,7 @@ need to edit SQL.
 
 ```
  supython/
- ├── manage.py                       # Django-style entrypoint (sets SUPYTHON_SETTINGS_MODULE)
+ ├── manage.py                       # optional cli entrypoint (sets SUPYTHON_SETTINGS_MODULE)
  ├── docker-compose.yml              # Postgres + PostgREST (dev stack)
  ├── docker-compose.prod.yml         # hardened single-host production stack
  ├── docker-compose.test.yml         # dedicated test Postgres on port 54323
@@ -521,7 +520,7 @@ need to edit SQL.
      ├── app.py                      # FastAPI factory
      ├── cli.py                      # typer: up, dev, keygen, admin, worker, test, …
      ├── extensions.py               # eager-import dotted module paths at boot
-     ├── settings_module.py          # Django-style user settings (EXTENSIONS, EXTRA_ROUTERS, …)
+     ├── settings_module.py          # user settings (EXTENSIONS, EXTRA_ROUTERS, …)
      ├── health.py                   # /livez, /readyz, /health endpoints
      ├── logging_config.py           # structured JSON log setup
      ├── security_headers.py         # HSTS, CSP, etc.
@@ -570,7 +569,7 @@ need to edit SQL.
 
 ## Plugins & extensions
 
-supython uses a Django-style settings module to declare your app's extensions:
+supython uses a settings module to declare your app's extensions:
 
 ```python
 # <name>/settings.py — scaffolded by `supython init`
@@ -669,7 +668,7 @@ supython test reset                               # stop test DB + delete volume
    `auth.uid()` returns the user's id inside RLS policies.
 4. RLS policies on `public.todos` use `auth.uid()` to scope every query.
 
-This is exactly the model Supabase uses, in ~400 lines of Python.
+
 
 ## Docker image
 
@@ -731,7 +730,7 @@ unit tests always run in isolation.
 **CI:** runners with Docker run `supython test up && supython test run`;
 runners without Docker run `pytest tests/unit` for a meaningful subset.
 
-## Roadmap [shipped v0.1.0]
+## Roadmap [shipped v0.1.2]
 
 - ✅ Email/password auth, PostgREST contract, RLS demo
 - ✅ OAuth, password reset, magic link, OTP, reuse detection, email backend, test suite
@@ -742,12 +741,12 @@ runners without Docker run `pytest tests/unit` for a meaningful subset.
 - ✅ Production observable: structured JSON logs, `/livez`/`/readyz`/`/health`, security headers, input size guards, audit log completeness, OAuth PKCE, secret rotation runbooks
 - ✅ (partial) Multi-arch Docker images, admin control plane (Vue 3 SPA — database, auth, storage, functions, realtime, jobs, backups, log tail), CI buildx workflow; benchmarks + security audit pass + dependency budget CI remaining
 - *(deferred)* — Realtime v2 over logical replication
-- v0.1.0 Release — final sweep, tag, publish wheel, production deployment with no patches
-- ✅ **TypeScript SDK** — `@supython/sdk` wrapping `@supabase/postgrest-js` + `@supabase/realtime-js`
+- v0.1.2 Release — final sweep, tag, publish wheel, production deployment with no patches
+- ✅ **TypeScript SDK** — `@supython/sdk` wrapping `@supabase/postgrest-js` + `@supabase/realtime-js` 
 
-### Post v0.1.0
+### Post v0.1.2
 
-- **v1.1+** — Admin control plane polish (backend + frontend shipped in v0.1.0; tests + remaining DoD items deferred)
+- **v1.1+** — Admin control plane polish (backend + frontend shipped in v0.1.2; tests + remaining DoD items deferred)
 - **Realtime v2** — logical replication (demand-driven; swap when trigger overhead or >8KB payload data warrants it)
 - **Prometheus `/metrics`** + **OpenTelemetry** — optional extras
 

{supython-0.1.1 → supython-0.1.2}/README.md

@@ -1,9 +1,9 @@
 # supython
 
-> A lightweight, Postgres-first BaaS framework for Python. **v0.1.0 release**
+> A lightweight, Postgres-first BaaS framework for Python. **v0.1.2 release**
 
-supython is the inverse of Django: **the database owns the schema, Python owns
-the things SQL is bad at**. It leans on [PostgREST](https://postgrest.org)
+**the database owns the schema, Python owns the things SQL is bad at**. 
+It leans on [PostgREST](https://postgrest.org)
 for auto-generated REST APIs and on Postgres' own RLS for authorization,
 while a small FastAPI service in Python handles auth, JWT issuance, realtime,
 storage, functions, workers, and an optional admin control plane.
@@ -11,7 +11,7 @@ storage, functions, workers, and an optional admin control plane.
 supython is for a specific person with a specific problem:
 > A developer who wants to build a CRUD-heavy web app (most apps are), who thinks in SQL, who wants Postgres to own authorization, and who wants auth + storage + custom logic without assembling the integration themselves.
 
-Shipped [v0.1.0]:
+Shipped [v0.1.2]:
 
 **Core platform**
 - **Email/password auth** — signup, login, refresh-token rotation with **reuse detection**
@@ -30,7 +30,7 @@ Shipped [v0.1.0]:
 
 **Realtime**
 - **WebSocket Realtime** — `postgres_changes`, `broadcast`, `presence` with per-subscriber RLS filtering
-- **Phoenix Channels wire format** — unmodified `supabase-js` / `supabase-py` SDKs connect
+- **Phoenix Channels wire format** 
 - **Generic trigger** — `realtime.enable('public.todos')` opts any table in
 - **Two-browser chat demo** — `examples/chat.html` (zero build step)
 
@@ -48,7 +48,7 @@ Shipped [v0.1.0]:
 - **Secret rotation** — JWT keys, symmetric secrets, Postgres passwords; all with zero-downtime runbooks
 - **Multi-arch Docker image** — `linux/amd64` + `linux/arm64`, non-root user, `tini` PID 1, ~64 MB
 
-**Admin control plane** (shipped in v0.1.0)
+**Admin control plane** (shipped in v0.1.2)
 - **Vue 3 + Vite SPA** at `/admin` — no runtime Node deps; pre-built static bundle in the wheel
 - **Database surface** — schema browser, table data with role switcher, SQL workspace (read-only default + write toggle), RLS policy editor with dry-run, migrations panel
 - **Auth surface** — user search, ban/unban/force-logout, refresh-token inspector, audit log, email template editing
@@ -101,7 +101,7 @@ cp .env.example .env
 # the value PostgREST will use (docker-compose.yml injects it via env).
 #
 # The scaffold creates:
-#   manage.py         — Django-style CLI entrypoint (sets SUPYTHON_SETTINGS_MODULE)
+#   manage.py         — Optional CLI entrypoint (sets SUPYTHON_SETTINGS_MODULE)
 #   myapp/settings.py — declare EXTENSIONS, EXTRA_ROUTERS, EXTRA_MIDDLEWARE
 #   myapp/jobs.py     — example @job seed (register your background jobs here)
 #   myapp/hooks.py    — example @on("signup") seed (lifecycle hooks)
@@ -161,8 +161,7 @@ including filtering, sorting, refresh, and isolation between users.
 ## Realtime quickstart
 
 supython ships a WebSocket engine that speaks the **Phoenix Channels 5-tuple
-protocol** used by every official Supabase SDK.  Unmodified `supabase-js` and
-`supabase-py` clients connect without any shim.
+protocol**.
 
 ### 1. Opt a table into realtime
 
@@ -386,7 +385,7 @@ need to edit SQL.
 
 ```
  supython/
- ├── manage.py                       # Django-style entrypoint (sets SUPYTHON_SETTINGS_MODULE)
+ ├── manage.py                       # optional cli entrypoint (sets SUPYTHON_SETTINGS_MODULE)
  ├── docker-compose.yml              # Postgres + PostgREST (dev stack)
  ├── docker-compose.prod.yml         # hardened single-host production stack
  ├── docker-compose.test.yml         # dedicated test Postgres on port 54323
@@ -463,7 +462,7 @@ need to edit SQL.
      ├── app.py                      # FastAPI factory
      ├── cli.py                      # typer: up, dev, keygen, admin, worker, test, …
      ├── extensions.py               # eager-import dotted module paths at boot
-     ├── settings_module.py          # Django-style user settings (EXTENSIONS, EXTRA_ROUTERS, …)
+     ├── settings_module.py          # user settings (EXTENSIONS, EXTRA_ROUTERS, …)
      ├── health.py                   # /livez, /readyz, /health endpoints
      ├── logging_config.py           # structured JSON log setup
      ├── security_headers.py         # HSTS, CSP, etc.
@@ -512,7 +511,7 @@ need to edit SQL.
 
 ## Plugins & extensions
 
-supython uses a Django-style settings module to declare your app's extensions:
+supython uses a settings module to declare your app's extensions:
 
 ```python
 # <name>/settings.py — scaffolded by `supython init`
@@ -611,7 +610,7 @@ supython test reset                               # stop test DB + delete volume
    `auth.uid()` returns the user's id inside RLS policies.
 4. RLS policies on `public.todos` use `auth.uid()` to scope every query.
 
-This is exactly the model Supabase uses, in ~400 lines of Python.
+
 
 ## Docker image
 
@@ -673,7 +672,7 @@ unit tests always run in isolation.
 **CI:** runners with Docker run `supython test up && supython test run`;
 runners without Docker run `pytest tests/unit` for a meaningful subset.
 
-## Roadmap [shipped v0.1.0]
+## Roadmap [shipped v0.1.2]
 
 - ✅ Email/password auth, PostgREST contract, RLS demo
 - ✅ OAuth, password reset, magic link, OTP, reuse detection, email backend, test suite
@@ -684,12 +683,12 @@ runners without Docker run `pytest tests/unit` for a meaningful subset.
 - ✅ Production observable: structured JSON logs, `/livez`/`/readyz`/`/health`, security headers, input size guards, audit log completeness, OAuth PKCE, secret rotation runbooks
 - ✅ (partial) Multi-arch Docker images, admin control plane (Vue 3 SPA — database, auth, storage, functions, realtime, jobs, backups, log tail), CI buildx workflow; benchmarks + security audit pass + dependency budget CI remaining
 - *(deferred)* — Realtime v2 over logical replication
-- v0.1.0 Release — final sweep, tag, publish wheel, production deployment with no patches
-- ✅ **TypeScript SDK** — `@supython/sdk` wrapping `@supabase/postgrest-js` + `@supabase/realtime-js`
+- v0.1.2 Release — final sweep, tag, publish wheel, production deployment with no patches
+- ✅ **TypeScript SDK** — `@supython/sdk` wrapping `@supabase/postgrest-js` + `@supabase/realtime-js` 
 
-### Post v0.1.0
+### Post v0.1.2
 
-- **v1.1+** — Admin control plane polish (backend + frontend shipped in v0.1.0; tests + remaining DoD items deferred)
+- **v1.1+** — Admin control plane polish (backend + frontend shipped in v0.1.2; tests + remaining DoD items deferred)
 - **Realtime v2** — logical replication (demand-driven; swap when trigger overhead or >8KB payload data warrants it)
 - **Prometheus `/metrics`** + **OpenTelemetry** — optional extras
 

{supython-0.1.1 → supython-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "supython"
-version = "0.1.1"
+version = "0.1.2"
 description = "A lightweight Postgres-first BaaS framework for Python"
 readme = "README.md"
 requires-python = ">=3.11"