**Note: This is an experimental release of HTML5 deployment support and is not recommended for production use.**

(e.g. `wait 10`)

* externals (including revdb)

Deploying an app to an HTML5 standalone is straightforward:

Your application will be packaged up and placed in the selected output folder.

The HTML5 standalone contains four files:

* A test HTML page. This can be opened in a browser and will correctly prepare, download and start your HTML5 app in a convenient test environment.

Some browsers, such as Google Chrome, do not permit pages to download resources from `file://` URLs. You won't be able to test your application in these browsers unless you run a local HTTP server.

This will let you access your standalone by opening your web browser and visiting <http://localhost:8080>.

Please report bugs to the [LiveCode Quality Centre](http://quality.livecode.com/). Make sure to select "HTML5 Standalone" when you're creating your bug report!

JavaScript applications running in a browser don't have access to the host system's filesystem. Instead, the filesystem-related features of LiveCode, such as `open file`, use a virtual filesystem (VFS) that exists only in memory. This filesystem is initialised before the engine starts, and is reset and its content discarded when the engine stops (when the user closes the browser view or navigates to a different page).

In general, if you wish to add new files or directories to the `standalone.zip` archive, it is best to add them outside the `/boot/` directory tree.

The default HTML5 page provided by the HTML5 standalone builder is designed for testing and debugging purposes. However, you may want to embed the standalone engine in a more visually appealing page. To do this, you require three elements: 1) a canvas, 2) a JavaScript `Module` object, and 3) an HTML `<script>` element that downloads the engine.

The engine renders into a HTML5 `<canvas>` element. There are three important considerations when creating the canvas:

By default, most web browsers will indicate when the canvas has focus by displaying a highlighted outline. This helps users identify which part of the web page is capturing their key presses. You can usually disable this outline by adding `outline: none;` to the canvas's CSS styles.

The top-level JavaScript `Module` object contains the parameters that control how the engine runs. At minimum, you need only specify the `Module.canvas`, which should be your canvas element.

};

</script>

The engine is quite a large JavaScript file, so it's downloaded asynchronously in order to let the rest of the page finish loading and start being displayed.

Make sure to replace `<version>` as appropriate.

Here's the complete skeleton web page for an HTML5 standalone:

</body>

</html>

Currently, the engine files are almost 30 MB, which is a lot to download before the engine can start. It is possible to speed up the download by enabling deflate compression in the web server configuration.

* For the Apache web server, configure `mod_deflate` to serve [pre-compressed content](https://httpd.apache.org/docs/2.4/mod/mod_deflate.html#precompressed)

* For the NGINX web server, add [`gzip_static on;`](https://www.nginx.com/resources/admin-guide/compression-and-decompression/#send) to your configuration.

There are a number of LiveCode-specific `Module` attributes that you can modify to affect how the engine behaves: