A Helion Stackato deployment can be extensively customized and themed. Administrators can add or remove runtimes, frameworks and services from the system, and change the look and content of the Management Console interface.
The Helion Stackato CLI client version number and the paths or URLs to the downloadable archives for each platform.
Local paths are relative to the
(Router node, see Renaming the Client), but HTTP URLs can also be used for
externally hosted files.
The client executables served from the VM are the latest version available at the time of the Helion Stackato VM release, but updated clients may become available between releases. The current release of the Helion Stackato CLI client is always available for download.
The HTML/EJS to show on the Welcome page. The settings variables and
username variable (current user) are
available via EJS, but plain HTML will work for simple use cases.
The HTML/EJS to show on the Support page. The settings variables and
support_email variable (see Settings
> Controller) are available.
CSS defined here will be applied to the page after the default CSS has been loaded, and override and replace any style. Use this to change the layout and color of any element in the Management Console. Use web development tools like Firebug or Chrome DevTools to inspect elements and find the relevant styles.
The following variables (with their default values) are available in the
EJS templates on the settings object (for example,
You can click Load Default for each individual setting (refresh icon to the left of the value field) which will replace the customized value with the default for that setting. To apply the changes, click Save.
Clicking Load Defaults (in red) at the top of the page deletes all customizations and loads defaults for all settings.
As a failsafe for when style changes have obscured the interface, admins can also reset specific settings by loading a URL in the following format:
setting_name with one of the variables above and that value
will be reset to the default.
To expose customized error pages, create the following HTML files in
/home/stackato/stackato/static/vendor/errors/ on each Router node:
When present, these files will be used to display the corresponding HTTP errors.
The default error page files in
/home/stackato/stackato/code/console/errors/ can be used as a
reference, but should not be modified directly as changes may be lost
during upgrades or patches.