Configuring Website Files

Website File configuration is broken into two parts, the browser side address and the server side source. For this page, "Domain" refers to the Domain popup menu that lists Domains and Subdomains.

Web Address

Select a domain and optionally add a path. Together these form the URL that visitors will access. Website Files configured with a domain but no path will prevent a Web App from running on that domain.

Lifeboat allows a configuration to have a Web Path that is within another Website Files configuration. This setup is for using using multiple PHP scripts on the same website. When doing so, place each script under its own Website Files configuration.

When serving static files for a Xojo Web app it is best practice to serve from a subpath on the same domain. Doing so satisfies and simplifies a lot of cross-domain security.

Some web paths are reserved for Xojo and can cause problems if you use these subpaths:

• /_* (anything that starts with an underscore)
• /api/
• /framework/
• /icons/
• /special/
• /xojo/

Source Path

Initially, the source path will be public_html under the user home folder. Lifeboat will suggest a source path specific to the selected domain when you click the "Suggest" button.

To access this location in Xojo code use SpecialFolder.UserHome.Child("public_html")

When the source directory does not yet exist Lifeboat will offer to create it. To prevent unintentional misconfiguration, Lifeboat will only be able to create the target directory. Everything else on the path must already exist.

Tab Details

Options
Error Pages
mod_rewrite

Save the Changes

To save changes to the configuration click the "Save" button. Lifeboat will write and upload the nginx configuration. Changes will be lost by pressing the Cancel button or navigating away from the Static Files view.