You can configure your Hyperscience instance to meet the infrastructure and business needs of your organization.
The options available to you depend on whether you have an on-premise / private cloud instance or a SaaS instance of Hyperscience.
On premise / private cloud instances
Hyperscience allows you to customize many aspects of your on-premise / private cloud implementation to meet the needs of your organization.
The table below lists the various ways in which you can tailor your configuration, along with links to articles with more information.
Making changes to the “.env” file
Configuration of on-premise / private cloud instances is managed through the “.env” file in the supplied bundle. The bundle contains an example “.env” file that needs to be filled in. You should delete any sections that you are not using. You may also need to add entries for some of the optional features if enabled. To learn more, see Editing the “.env” file and running the application.
Configuration options for on-premise / private cloud instances
Configuration | Required? | Options |
|---|---|---|
Yes | ||
Yes | ||
Yes | ||
Only if your organization uses security certificates (e.g., TLS) |
| |
Only if you plan on storing submission images on an external server | ||
No |
| |
Only if you are instructed to change these settings by a Hyperscience representative |
| |
Only if you need to limit the percentage of CPU resources consumed by the Hyperscience application |
| |
Only if you want to set your application’s time zone to a time zone other than US/Eastern |
| |
No |
| |
No |
|
SaaS instances
If you have a SaaS instance of Hyperscience, Hyperscience configures your instance for you. You can work with Hyperscience to customize the parts of your system listed in the table below.
Configuration options for SaaS instances
Configuration | Required? | Options |
|---|---|---|
Yes | ||
Only if you plan on storing submission images on an external server | ||
No |
|