tent export

Writes a site, or the public part of an app, out as plain files for any host of files.

Usage

tent export --out <folder> [--base <path>] [--origin <scheme and name>] [--names any] [--data <folder>]

The command builds the project as a release, gives that bundle to the engine that runs on the data folder, has it write the site out with its data, and drops the version again. With no engine running it starts one for the length of the command, on the development data. So an export never holds a development build: no source of a screen file, and the page code in its small form. --out is a folder of the project, or a whole path.

For each screen that anyone may see, as nobody, and for a screen with values in its address once for each row of seo.addresses, the export writes:

What is left out is named in skipped with the reason: a screen that is not open to anyone, one with values and no seo.addresses, an address with a value that holds a slash, a backslash, two dots or a control character, one with a sign that cannot stand in the name of a file on every system (<, >, :, ", |, ?, *, or a dot or a space at its end), and the second of two addresses that differ only in capitals.

Run again, an export writes the site anew: it keeps the list of what it wrote in _t/export.json, removes each file of the list before that it does not write again, and touches no other file of the folder.

With no engine behind an exported page nothing is live and no call can be made. A page finds out once, when it comes alive, by asking /_t/health under its base: any answer but the engine's own means none, and the page then opens no connection and asks nothing again. A press that needs a call fails at once with code.T0001. A move to another page takes the file under _t/s/, and where there is none it loads the address as a whole page.

With the engine behind the same address everything works as in a served app: the host sends every address that it holds no file for on to the engine, with the base taken off. Calls, the live connection and sign-in then stay on one site. After a new version an exported page follows the running version from its first call. What the host sends on is counted as every request is (code.T0005): /_t/health, which each page asks once, by nothing, a screen that the engine draws on screensPerMinute of its address, and a call on its caller. A host that the engine is told of as a proxy and that states each visitor's address in X-Forwarded-For has each visitor counted alone; one that states none is one address for all of them.

A host of files sends its own headers, so the policy of each page is a line of its head. Who may frame a page cannot be said that way, and is the host's to set.

Options

Example

tent export --out site --base /shop --origin https://shop.example.com

A program that holds the app writes the same with app.export('site', { base: '/shop', origin: 'https://shop.example.com', version }), which answers { pages, skipped, findings }.

Output

With --json:

{ "ok": true, "value": { "pages": ["/", "/about"], "skipped": [{ "what": "deskScreen", "why": "The screen is not open to anyone." }], "findings": [] }, "findings": [] }

Errors

See also

topic.commands, topic.engine, option.screen.seo, code.T6016