Informat AI Low-Code Docs

English

简体中文

English

简体中文

Appearance

Website and Resource Hosting ​

Informat's Website and Resource Hosting feature provides static resource hosting services, server-side rendering (SSR), and other capabilities, enabling you to quickly launch static or dynamic websites.

In some scenarios, Informat's pages may not meet your diverse display needs. In such cases, you'll need to use Informat's website functionality. With Informat's powerful editing capabilities, you don't need to write any backend code. You can display your data on Informat as a website, allowing users to access this website page anytime, anywhere to browse data.

Informat provides hosting services for static resources such as HTML, JS, CSS, and images used in website development.

TIP

Website pages are not limited to specific technology stacks. You can choose the appropriate technology stack for your team's actual situation to develop website pages. If you use a pre-compiled technology stack like Vue or React, you need to upload the compiled files to the website module.

Resources and URLs ​

Creating a website module is equivalent to creating a site with a root directory of ${host}/web0/website/${appId}/${websiteId}/.

Where ${host} is the platform's domain name or IP, ${appId} is the application ID, and ${websiteId} is the website module's identifier.

If I upload an index.html file to the website module, its corresponding URL is ${host}/web0/website/${appId}/${websiteId}/index.html, and its relative path within the site is ./index.html.

Additionally, all resources uploaded to the website module are saved in Shared Storage. The actual storage path of resources can be obtained through script methods. For specific usage, please refer to informat.website.getStoragePath.

Application Distribution Note

appId is automatically generated by the system and may be different in different environments. To ensure that applications distributed to any environment can access specified resources, you need to set the access resource path using dynamically obtained appId in the code that references website resources.

If resources within the site depend on each other, it is recommended to use relative paths.

We will use a simple static site example to illustrate the dependencies between resources.

text
.
├──css
│   └── index.css
└──index.html
css
body {
  background-color: #5b8ff9;
}

body h1 {
  color: #fff;
}
html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <title>Resource Dependencies</title>
    <link rel="stylesheet" type="text/css" href="./css/index.css" />
  </head>
  <body>
    <h1>Hello World!</h1>
  </body>
</html>

Code Management ​

  • Supports directly uploading resources or files from a locally written project directory to the website module for resource hosting
  • Supports directly synchronizing directories from Git to the website module for resource hosting

File Synchronization Note

When using Git synchronization, hidden files starting with . such as .git will not be synchronized.