Installation and management of HAXiam have scripts to help with their setup just like other parts of the HAX ecosystem
HAXiam allows for empowering users to create sites but in order to ensure they don't step on each other's namespaces, addresses can get kind of long. This is by design to support a multi-tenant environment for building the site, but often is annoying when sharing addresses out to others. That's where vanity domains come in, though they require server configuration.
VirtualHost
block as to where in the file system to point for this domainVirtualHost
definition: SetEnv HAXSITE_BASE_URL /
/
is the base path seen in the URL when accessing the root of the site. /
will be the most common for this when doing something like example.com
pointing to a site within a HAXiam instanceThe HAXSITE_BASE_URL variable is required to help the front-end resolve where the <base>
tag is going to be resolving to. This configuration allows HAXiam to manage the path for viewing and authorship, while at the same time helping the PWA nature of HAXsite still be able to resolve where the files are for the site no matter the URL.
Both HAXiam as well as HAXcms can have customization applied to HAXiam's configure directory in order to ensure maintainable upgrades of both the core platform as well as HAXcms which it is managing a copy of.
Example implementations of these files are written into new instances at the time the system is created and can be found here.