@getxflow/cli 0.26.0 → 0.27.0

package/dist/commands/pages.js

@@ -64,7 +64,7 @@ async function pagesList(args) {
     }
     if (pages.length === 0) {
         (0, ui_1.note)('The organization has no pages yet');
-        (0, ui_1.note)((0, ui_1.dim)('  A new one: xflow pages create "Price list"'));
+        (0, ui_1.note)((0, ui_1.dim)('  A new one: xflow pages create "Price list" ./dist'));
     }
     else {
         (0, ui_1.table)(pages.map((page) => [
@@ -83,18 +83,24 @@ async function pagesList(args) {
     }
 }
 async function pagesCreate(args) {
-    const title = args.words.slice(1).join(' ').trim();
-    if (!title) {
-        throw new errors_1.CliError('A title is required', 'For example: xflow pages create "Price list" --slug price-list');
+    const source = args.words.length > 2 ? args.words[args.words.length - 1] : undefined;
+    const title = args.words.slice(1, -1).join(' ').trim();
+    if (!source || !title) {
+        throw new errors_1.CliError('A title and what to put on the page are required', 'A page is born with its first version: xflow pages create "Price list" ./dist --slug price-list');
     }
+    const upload = readUpload(source);
     const slug = (0, args_1.flagString)(args, 'slug');
-    const { page } = await (0, api_1.apiJson)(pagesClient(), '/api/v1/pages', {
-        method: 'POST',
-        body: slug ? { title, slug } : { title },
+    const query = new URLSearchParams(slug ? { title, slug } : { title });
+    (0, ui_1.step)(`Uploading ${upload.label}`);
+    const result = await (0, api_1.apiUpload)(pagesClient(), `/api/v1/pages?${query}`, upload.body, {
+        'Content-Type': contentTypeOf(upload),
     });
-    (0, ui_1.ok)(`Page "${page.title}" created`);
-    (0, ui_1.out)(page.url);
-    (0, ui_1.note)((0, ui_1.dim)(`  Nothing is on it yet: xflow pages deploy ${page.slug} <folder, .zip or .html>`));
+    (0, ui_1.ok)(`Page "${result.page.title}" is live: ${result.file_count} file(s), ${(0, ui_1.formatBytes)(result.size_bytes)}`);
+    (0, ui_1.out)(result.page.url);
+    (0, ui_1.note)((0, ui_1.dim)(`  Anyone with the address sees it within seconds. The next version: xflow pages deploy ${result.page.slug} <path>`));
+}
+function contentTypeOf(upload) {
+    return upload.kind === 'zip' ? 'application/zip' : 'text/html';
 }
 function assertUploadSize(bytes) {
     if (bytes <= MAX_UPLOAD_BYTES)
@@ -161,7 +167,7 @@ async function pagesDeploy(args) {
     (0, ui_1.step)(`Uploading ${upload.label}`);
     const query = comment ? `?comment=${encodeURIComponent(comment)}` : '';
     const result = await (0, api_1.apiUpload)(client, `${pagePath(ref)}/deploy${query}`, upload.body, {
-        'Content-Type': upload.kind === 'zip' ? 'application/zip' : 'text/html',
+        'Content-Type': contentTypeOf(upload),
     });
     if (result.status === 'unchanged') {
         (0, ui_1.ok)(`Nothing changed: version ${result.revision} is already on the address`);

package/dist/help.js

@@ -91,8 +91,8 @@ ${(0, ui_1.bold)('Database')}
 
 ${(0, ui_1.bold)('Pages')}
   xflow pages                     public sites of the organization at <name>.xflowpage.ru
-  xflow pages create <title> [--slug name]
-                                  a new page, empty until the first upload
+  xflow pages create <title> <folder|.zip|.html> [--slug name]
+                                  a new page with the site on it, live at once
   xflow pages deploy <page> <folder|.zip|.html> [-m "what changed"]
                                   upload the site: live at once, there is no publish step
   xflow pages status <page>       the page and its versions
@@ -232,15 +232,16 @@ signing in and outside the platform. A project is the opposite: it opens only in
 platform, for the members of the organization.
 
   xflow pages                          the pages, their state and address
-  xflow pages create <title>           a new page, empty until the first upload
+  xflow pages create <title> <path>    a new page with its first version: there are no
+                                       empty pages
       --slug <name>                    the name in the address; without it the name is made
                                        from the title, with a random tail
-  xflow pages deploy <page> <path>     upload a folder with index.html at the top, its .zip,
-                                       or one .html file
+  xflow pages deploy <page> <path>     upload a new version
       -m <text>                        what changed, one short line: it names the version
   xflow pages status <page>            the page and its versions
   xflow pages rollback <page> <N>      put version N back on the address
 
+${(0, ui_1.bold)('<path>')} is a folder with index.html at the top, its .zip, or one .html file.
 ${(0, ui_1.bold)('<page>')} is the name from the address or the id. ${(0, ui_1.bold)('--json')} on list and status
 prints the answer as JSON. A page belongs to the organization, not to a project, so there is
 no ${(0, ui_1.bold)('--project')}: the key is picked as for every other command (${(0, ui_1.bold)('xflow help org')}).
@@ -255,7 +256,9 @@ build it and upload what the build writes. Dot entries are skipped. At most 5 MB
 unpacked and 1000 files.
 
 The page is public, so a file holding a secret key is refused whole: every visitor would read
-it. Search engines are asked not to index pages, so do not promise SEO.
+it. A function key is the exception: it opens that one function to every visitor, which is
+what a form on a landing page needs. Search engines are asked not to index pages, so do not
+promise SEO.
 
 A page takes the key of the whole organization, the one ${(0, ui_1.bold)('xflow login')} issues. The
 section is in beta: XFlow support switches it on for an organization. Switching a page off

package/dist/version.js

@@ -2,6 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.DEFAULT_API_URL = exports.CLI_VERSION = void 0;
 /** Keep in sync with cli/package.json. */
-exports.CLI_VERSION = '0.26.0';
+exports.CLI_VERSION = '0.27.0';
 /** Overridden by XFLOW_API_URL or the `api` field in xflow.json. */
 exports.DEFAULT_API_URL = 'https://app.getxflow.com';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getxflow/cli",
-  "version": "0.26.0",
+  "version": "0.27.0",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -22,7 +22,7 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 0.26.0, so the copy you are reading can be older than
+These instructions ship with xflow CLI 0.27.0, so the copy you are reading can be older than
 the CLI answering your commands.
 
 When the CLI says this file does not match it, run `xflow skills --refresh` and then **read
@@ -527,10 +527,11 @@ presentation, an invoice for people outside the organization. Anyone with the ad
 without signing in and outside the platform. A project is the opposite, it opens only inside the
 platform: pick a page when the audience is outside the organization.
 
-- `xflow pages create "Price list"` makes an empty page and prints its address. `--slug
-  price-list` picks the name, otherwise it comes from the title with a random tail.
-- `xflow pages deploy <page> <folder|.zip|.html> -m "what changed"` uploads the built site.
-  **It is public the moment the command finishes**: no draft, no publish step. Upload when the
+- `xflow pages create "Price list" ./dist` makes a page with the built site on it and prints its
+  address: there are no empty pages. `--slug price-list` picks the name, otherwise it comes from
+  the title with a random tail.
+- `xflow pages deploy <page> <folder|.zip|.html> -m "what changed"` uploads a new version.
+- **Both are public the moment the command finishes**: no draft, no publish step. Upload when the
   user wants the page out, and give them the address the CLI printed.
 - `xflow pages status <page>` lists the versions, `xflow pages rollback <page> <N>` puts one back
   in seconds; the files of the last 5 are kept.
@@ -538,7 +539,9 @@ platform: pick a page when the audience is outside the organization.
   or functions on a page. Upload what the build writes (`dist`), never a folder with
   `package.json`. At most 5 MB zipped, 25 MB unpacked, 1000 files.
 - Everything in a page is readable by every visitor. Never put a key, token or password into
-  it: a known key format gets the upload refused, anything else simply leaks.
+  it: a known key format gets the upload refused, anything else simply leaks. A function key is
+  the exception: a person issues it in the settings of the function, and a form on a page may
+  call that function with it. So can every visitor.
 - Search engines are asked not to index pages: do not promise SEO.
 - The MCP `pages` tool uploads one self-contained HTML document up to 150 KB.
 - Pages take the key of the whole organization, the one `xflow login` issues. The section is in