saasaloy 0.5.1 → 0.6.0

package/README.md

@@ -7,6 +7,7 @@
 [![npm version](https://img.shields.io/npm/v/saasaloy)](https://www.npmjs.com/package/saasaloy)
 [![CI](https://github.com/mimukit/saasaloy/actions/workflows/ci.yml/badge.svg)](https://github.com/mimukit/saasaloy/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE.md)
+[![CodeRabbit Pull Request Reviews](https://img.shields.io/coderabbit/prs/github/mimukit/saasaloy?utm_source=oss&utm_medium=github&utm_campaign=mimukit%2Fsaasaloy&color=FF570A&link=https%3A%2F%2Fcoderabbit.ai&label=CodeRabbit+Reviews)](https://coderabbit.ai)
 
 > [!WARNING]
 > **Saasaloy is at a very early stage.** It is a working proof of concept, not a finished product. Use it at your own risk, and do not build a production project on it yet. The CLI, the module contracts, the generated code and the conventions can all change or break between releases until a stable `1.x.x` version ships. Pin the version you install, read the changelog before you update, and expect to do some manual merging along the way.
@@ -59,13 +60,13 @@ pnpm dev
 Then add modules as the product grows:
 
 ```bash
-saasaloy list                
+saasaloy list
 # what the registry offers, and what you already have
 
-saasaloy add waitlist        
+saasaloy add waitlist
 # pulls api, validators and database, then asks for a database driver
 
-saasaloy add admin           
+saasaloy add admin
 # pulls auth, then an auth-gated admin SPA
 ```
 
@@ -98,7 +99,7 @@ Each row installs on top of the previous one. Nothing from a later row lands in
 | Email | Cloudflare Email Sending, Plunk, or a console logger |
 | Storage | Cloudflare R2, or in memory |
 | Background work | Cloudflare Queues and Cron Triggers, or an in-process runner |
-| Infra | wrangler per workspace, or Pulumi via the `infra` module |
+| Deploy | wrangler, through `pnpm deploy:production` |
 | Monorepo | Turborepo + pnpm |
 
 ## Modules
@@ -107,9 +108,9 @@ Modules come in tiers. A **capability** scaffolds a workspace and sets conventio
 
 | Tier | Modules |
 |---|---|
-| Capability | `api`, `database`, `validators`, `logger`, `auth`, `admin`, `email`, `sms`, `queue`, `kv`, `storage`, `billing`, `infra` |
+| Capability | `api`, `database`, `validators`, `logger`, `auth`, `admin`, `email`, `sms`, `queue`, `kv`, `storage`, `billing`, `payment` |
 | Feature | `waitlist`, `teams`, `multitenant`, `rbac`, `api-keys`, `entitlements`, `email-react`, `ratelimit`, `feature-flags` |
-| Provider | `email-console`, `email-cloudflare`, `email-plunk`, `logger-console`, `sms-console`, `sms-khudebarta`, `queue-cloudflare`, `queue-memory`, `kv-cloudflare`, `kv-memory`, `storage-cloudflare`, `storage-memory`, `billing-console`, `billing-stripe` |
+| Provider | `email-console`, `email-cloudflare`, `email-plunk`, `logger-console`, `sms-console`, `sms-khudebarta`, `queue-cloudflare`, `queue-memory`, `kv-cloudflare`, `kv-memory`, `storage-cloudflare`, `storage-memory`, `billing-console`, `billing-stripe`, `payment-console`, `payment-manual` |
 | Driver | `database-d1`, `database-postgres` |
 
 What each module gives you and what it depends on is on the [Modules](https://github.com/mimukit/saasaloy/blob/main/docs/wiki/modules.md) page. Which ones need a paid Cloudflare plan or a third-party account is in the [Reference](https://github.com/mimukit/saasaloy/blob/main/docs/wiki/reference.md#email-providers). The short version: the base, `api`, `database-d1`, `auth`, `admin`, `waitlist` and `teams` run on the free tier, and every local provider runs with no account at all.
@@ -122,7 +123,7 @@ The default registry is this repo. `saasaloy add waitlist` fetches `modules/wait
 
 ## Deploy
 
-Each deployable workspace owns its `wrangler.jsonc` and `deploy` script, or the `infra` module deploys every Worker with one Pulumi program. See [Deploy to Cloudflare](https://github.com/mimukit/saasaloy/blob/main/docs/wiki/how-to/deploy-to-cloudflare.md).
+`pnpm deploy:production` deploys every Worker in the project with wrangler. It loads the production values from the value source in memory, checks every one of them before anything builds, and uploads each Worker's secrets with its code. Wrangler creates the D1, KV, R2 and queue resources on the first deploy. Each deployable workspace keeps its own `wrangler.jsonc` and a `deploy` script that runs `env-deploy <service>`. See [Deploy to Cloudflare](https://github.com/mimukit/saasaloy/blob/main/docs/wiki/how-to/deploy-to-cloudflare.md).
 
 ## Documentation