Publish multiple sites

Fast-Https supports configuring and publishing several applications through config file inclusion, much like Nginx. You can of course put every site into the main fast-https.json, but once the number of applications grows that single file becomes tedious to maintain.

1 Enable the config directory

Inside /fast-https/config/ there is a conf.d folder that holds one file per site. Suppose we want to publish two proxied sites, www.a.com and www.b.com. First check whether the main fast-https.json contains the following option:

{
  "http": {
    "include": [
      "./config/conf.d"
    ]
  }
}

If it is missing, add it manually. The main configuration file then looks like this:

{
  "log_root": "./logs",
  "pid": "./fast-https.pid",
  "http": {
    "include": [
      "./config/conf.d"
    ]
  }
}

2 Create one file per site

In the conf.d folder create a configuration file per site, named after the domain — for example www.a.com.json and www.b.com.json.

For a reverse proxied site:

{
  "listen": 80,
  "server_name": "www.a.com",
  "location": [
    {
      "type": "proxy",
      "url": "/",
      "proxy_pass": "http://192.168.1.11:5001",
      "proxy_set_header": [
        {
          "HeaderKey": "Host",
          "HeaderValue": "$proxy_host"
        }
      ]
    }
  ]
}

To publish a local static site without a proxy:

{
  "listen": 80,
  "server_name": "www.b.com",
  "location": [
    {
      "type": "local",
      "url": "/",
      "root": "/var/www/www.b.com",
      "index": ["index.html", "index.htm"]
    }
  ]
}

3 Reload and test

Choose RELOAD from the tray menu, then visit both configured domains to verify each site.

4 Option reference