@wervt/cli 0.2.4 → 0.2.5

package/dist/index.mjs

@@ -220,6 +220,7 @@ const deploy = defineCommand({
 		const labels = {
 			extract: "Extracting",
 			migrate: "Migrating database",
+			storage: "Setting up storage",
 			activate: "Activating"
 		};
 		const decoder = new TextDecoder();
@@ -241,6 +242,10 @@ const deploy = defineCommand({
 					if (process.env.GITHUB_OUTPUT) await appendFile(process.env.GITHUB_OUTPUT, `url=${event.url}\nrelease=${event.release}\n`);
 					return;
 				}
+				if (event.step === "storage-failed") {
+					p.log.warn(`Storage isn't set up: ${event.message}. The app runs; files won't work yet.`);
+					continue;
+				}
 				spinner.message(labels[event.step] ?? event.step);
 			}
 		}
@@ -561,7 +566,7 @@ const remove = defineCommand({
 		},
 		"drop-database": {
 			type: "boolean",
-			description: "Also drop the app's schema and all its data"
+			description: "Also drop the app's schema, its files and all its data"
 		},
 		yes: {
 			type: "boolean",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wervt/cli",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Deploy and manage apps on wervt.",
   "keywords": [
     "agents",

package/skill/SKILL.md

@@ -34,7 +34,8 @@ The app comes with `AGENTS.md`, skills in `.claude/skills/` and a deploy workflo
 `AGENTS.md` before writing code** and follow it: server routes, valibot validation, Drizzle schema
 and migrations, live data with shapes, users, logging, and what the isolate runtime can't do
 (no filesystem, no child processes, no long-running work, no WebSockets). Periodic work goes
-into tasks (`defineTask` + `nitro.scheduledTasks`), which wervt runs on schedule.
+into tasks (`defineTask` + `nitro.scheduledTasks`), which wervt runs on schedule. Files go into
+the app's own bucket with ablage (`pnpm add ablage`, no configuration).
 
 Before picking a name, run `wervt apps` so you don't overwrite an existing app. If the user named an
 existing app, work in its repository instead.