Host-resolved multi-site theming for Phoenix.
A request host is resolved to a Multitenancy.Site, each site points to a
theme living under themes/<name>/, and every theme is a self-contained
slice of the application with its own router, controllers, templates,
layouts, assets and gettext backend. Templates missing from a theme fall
back to the base application (see Multitenancy.HTML).
Summary
Functions
Hosts served by the platform router instead of a theme.
Whether path_info falls under one of the prefixes ("/admin" matches /admin/sites).
Path prefixes served by the platform router on every host, such as an admin area or health checks shared by all sites.
The configured Multitenancy.SiteResolver implementation.
Fetches the theme definition for name.
Same as theme/1 but raises Multitenancy.ThemeNotFoundError.
The module conventionally defining the theme name, e.g. Themes.MyStore.
Names of the theme directories found under themes_path/0.
Directory holding the themes, relative to the project root.
Functions
Hosts served by the platform router instead of a theme.
Whether path_info falls under one of the prefixes ("/admin" matches /admin/sites).
Path prefixes served by the platform router on every host, such as an admin area or health checks shared by all sites.
The configured Multitenancy.SiteResolver implementation.
@spec theme(String.t() | atom()) :: {:ok, Multitenancy.Theme.t()} | :error
Fetches the theme definition for name.
@spec theme!(String.t() | atom()) :: Multitenancy.Theme.t()
Same as theme/1 but raises Multitenancy.ThemeNotFoundError.
The module conventionally defining the theme name, e.g. Themes.MyStore.
Names of the theme directories found under themes_path/0.
Directory holding the themes, relative to the project root.