tovuk 0.1.60 → 0.1.61

package/README.md

@@ -1,10 +1,10 @@
 # tovuk
 
-Deploy Rust backends, static frontends, and fullstack apps to Tovuk.
+Deploy Rust workers, static frontends, and worker-static services to Tovuk.
 
 ```sh
-npx tovuk init my-app --template fullstack-rust-tanstack
-cd my-app/web && bun install && cd ..
+npx tovuk init hello-service --template worker-static-rust-tanstack
+cd hello-service/web && bun install && cd ..
 npx tovuk doctor --json
 npx tovuk deploy --wait --json
 ```
@@ -13,7 +13,7 @@ The npm package installs the native Tovuk binary for the current platform.
 Node is required by npm to install the package, but the `tovuk` command itself
 does not delegate to `npx`, `tsx`, or any JavaScript runtime.
 
-Rust backends expect `Cargo.toml`, `Cargo.lock`, and `tovuk.toml`. They must
+Rust workers expect `Cargo.toml`, `Cargo.lock`, and `tovuk.toml`. They must
 pass `cargo fmt --all --check`, locked release-mode check/test/Clippy gates,
 listen on `0.0.0.0:$PORT`, and expose the configured health endpoint.
 
@@ -21,9 +21,9 @@ Static frontends must use TypeScript browser source, stable native type-aware
 TypeScript checks, native linting such as `oxlint`, `biome check`, or
 `deno lint`, and Fallow dead-code, semantic duplicate-code, and health gates.
 
-From a fullstack repo root, the same deploy command reads one root `tovuk.toml`,
-builds the backend and frontend roots, and returns one app URL with `/api/*`
-routed to the Rust backend.
+From a worker-static repo root, the same deploy command reads one root
+`tovuk.toml`, builds the worker and frontend roots, and returns one service URL
+with `/api/*` routed to the Rust worker.
 
 Preview before deploying:
 
@@ -42,24 +42,26 @@ npx tovuk logs --build job_1 --json
 Fix the first failed `agent_instruction`. If a build fails, inspect build logs,
 fix the first actionable log error, rerun doctor, then redeploy.
 
-Managed Postgres apps receive `DATABASE_URL`, `TOVUK_DATABASE_URL`, and
-`TOVUK_DATABASE_CONNECTION_LIMIT`. Use that limit as the max size for your
-database pool.
+Agents can create service SQLite databases, KV namespaces, queues, cron triggers,
+Durable Object namespaces, service bindings, and usage caps through the CLI.
 
 Agents can also inspect API capabilities, account identity, usage, account
-activity, apps, complete app overviews, deploys, builds, app/deploy/build logs,
-env metadata, custom domains, domain verification, app storage files and media,
+activity, services, complete service overviews, deploys, builds, service/deploy/build logs,
+env metadata, custom domains, domain verification, service storage files and media,
 billing checkout links, billing portal links, and support ticket create, list,
 and resolve actions
 through the same CLI.
 
-Manage app files and media without dashboard access:
+Manage service files and media without dashboard access:
 
 ```sh
-npx tovuk storage list --app app_1 --json
-npx tovuk storage upload --app app_1 ./logo.png uploads/logo.png --public --json
-npx tovuk storage download --app app_1 uploads/logo.png ./logo.png --json
-npx tovuk storage delete --app app_1 uploads/logo.png --json
+npx tovuk storage list --service service_1 --json
+npx tovuk storage upload --service service_1 ./logo.png uploads/logo.png --public --json
+npx tovuk storage download --service service_1 uploads/logo.png ./logo.png --json
+npx tovuk storage delete --service service_1 uploads/logo.png --json
+npx tovuk kv put --service service_1 CACHE user:1 '{"name":"Ada"}' --json
+npx tovuk kv get --service service_1 CACHE user:1 --json
+npx tovuk queue send --service service_1 jobs '{"task":"sync"}' --json
 ```
 
 When a free-tier limit blocks work, run:
@@ -71,7 +73,7 @@ npx tovuk billing checkout --json
 When Tovuk support is needed, include enough evidence for a support agent:
 
 ```sh
-npx tovuk support create "Deploy failed" "Agent retried deploy after doctor." --app app_1 --build job_1 --deploy deploy_1 --failing-command "tovuk deploy --wait --json" --first-log-line "cargo check failed in src/main.rs" --json
+npx tovuk support create "Deploy failed" "Agent retried deploy after doctor." --service service_1 --build job_1 --deploy deploy_1 --failing-command "tovuk deploy --wait --json" --first-log-line "cargo check failed in src/main.rs" --json
 ```
 
 When the issue is fixed, resolve the ticket:

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "tovuk",
-  "version": "0.1.60",
-  "description": "Deploy Rust backends, static frontends, and fullstack apps to Tovuk.",
+  "version": "0.1.61",
+  "description": "Deploy Rust workers, static frontends, and worker-static services to Tovuk.",
   "type": "module",
   "bin": {
     "tovuk": "bin/tovuk"
@@ -21,7 +21,7 @@
     "tovuk",
     "rust",
     "deploy",
-    "backend",
+    "worker",
     "hosting"
   ],
   "homepage": "https://tovuk.com",