Your Heretto Deploy Portal Environments

The Heretto Deploy Portal includes multiple environments for development and testing to facilitate your Heretto Deploy Portal development.

Heretto CCMS provides the tools you'll need to have a single source of truth from where you can manage all of your portal environments' configurations and styling. The Heretto team handles hosting and base code updates.

You can configure and customize your portal using your web browser and your portal environments. We recommend having Heretto CCMS open in one window and a portal environment open in another. You can make configuration and styling changes in the CCMS for the respective environments, then see the change immediately reflected in the portal.

Your portal comes with two environments:
Promote your styling and configuration changes to staging and perform testing against production-ready content.
This is the live environment where your visitors can access your content.

You can maintain different config.json files for different environments, which are tagged as environment specific in <data> elements in your sitemap. For more details on adding config.json files to your sitemap, refer to Customize Heretto Deploy Portal.

To customize and test your configuration changes, we recommend using multiple configurations files, along with a CSS file and a JavaScript file, if necessary. For example, you can use one for configuration, one for styling, and one for any JS you want to include. All three will be hosted in the Heretto CCMS and referenced in the sitemap using <data> elements.

We recommend using different config.json files, one for each portal environment, to manage your custom configurations of your portal environments. Most often, there are dev, qa, and prod versions of the configuration files. Each one controls a different portal environment, and each specific configuration file works in conjunction with the base configuration file.

Having multiple configuration files enables you to safely test changes in multiple different environments and save those changes separately from one another. For more information on using multiple configuration files, refer to Configuration Layers and Overrides.

Example of multiple configuration files in a sitemap