Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

Multisite on one installation

How one Exponential installation serves several sites through siteaccesses, matched by URL, host name or port; what that means for a host's isolation, logs, caches, billing and backups; and when separate installations…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/hosting/provisioning/multisite-on-one-installation.md

On this page

Multisite on one installation

This page is for hosts and administrators who run several sites from one Exponential installation, or who must decide whether to. It answers: how siteaccesses work, what the host has to configure, how logs and caches can be kept per site, and when separate installations are better.

Contents

  1. Siteaccesses in short
  2. Matching by URL, host or port
  3. Logs and caches per site
  4. One installation or several?

Siteaccesses in short

"A siteaccess is one way into the installation: a name, a set of settings in settings/siteaccess/<name>/, and a rule for which requests it answers" (10.2). The installer creates at least the public siteaccess and the administration (and an editor siteaccess with exp:install). More public siteaccesses can serve more sites, languages or designs from the same content repository.

The site package sevenx_multisite is built for this ("7x MultiSite Default Installation"; Site packages).

Matching by URL, host or port

The rules live in site.ini [SiteAccessSettings]; MatchOrder is uri;host;port as shipped.

LayoutExampleFor a host
URLwww.example.com/adminone host name, simplest behind any web server
Hostadmin.example.com"best for production and for HTTPS certificates per host"
Port:8081local work

Host matching, as in 10.2:

# settings/override/site.ini.append.php
[SiteAccessSettings]
MatchOrder=host;uri
HostMatchType=map
HostMatchMapItems[]
HostMatchMapItems[]=www.example.com;site
HostMatchMapItems[]=www.example.org;site_org
HostMatchMapItems[]=admin.example.com;admin

Each siteaccess sets its own [SiteSettings] SiteURL. Add every host name to the web server or Velocity, to DNS and to the certificate, clear the INI cache (php bin/php/ezcache.php --clear-tag=ini --allow-root-user) and test that each name reaches the right siteaccess. "The host name the browser sends must be exactly the one in HostMatchMapItems[], without a port and in lower case."

Behind a proxy or load balancer, list it in site.ini [HTTPHeaderSettings] TrustedProxies[], or the site sees the proxy's scheme and address (10.2).

Logs and caches per site

When each site has a VarDir of its own, these site.ini [FileSettings] settings keep its files apart (Logs, INI cache and expiry timestamps per site):

SettingDefaultEffect
UseGlobalLogDirenableddisabled writes the debug logs into the log directory of the site instead of var/log
LogVarDiremptya tree for the logs of every site, var_log/<site>/log
CacheVarDiremptya tree for the caches of every site, var_cache/<site>/cache (for example on a memory file system)
INICacheDirglobalsite caches each site's INI files in its own cache directory, so clearing one leaves the others alone

"Every setting keeps the behaviour of before" unless you set it. Settings per site inside extensions are described in Per-site settings inside extensions.

One installation or several?

One installation, several siteaccessesOne installation per site
Shared content and usersyesno
One update for all sitesyesone per site
Operating-system isolation between sitesno: one system user, one code baseyes (Multi-tenant isolation)
One customer's load affects the othersyesno, with separate pools or instances
Backups and restorestogetherper site
Billing "per site"define what a site is (Billing and metering options)simple

Rule of thumb for a host: several siteaccesses on one installation for one customer with several sites; separate installations for different customers.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x