Environments in HortiView¶
Change in progress
We currently change a lot in the staging process, so please be careful when using this part the documentation
We have multiple environments in HortiView that can be used by vendors to implement a staging process. To make your module work in each environment, you need to make sure that you are using the corresponding endpoints that are relevant for the environment the module is currently built for. You can, for example, either create a new build for every environment or access HortiView's environment variables at runtime to dynamically choose the correct endpoint.
Every API/environment is created following the same pattern, but the frontend likely has an alias to access it more easily: https://app-hv-c-[BACKEND-API]-[ENVIRONMENT]-weu-001.azurewebsites.net
[BACKEND-API]defines the API that needs to be accessed[ENVIRONMENT]is the environment: test, demo or prod
Test¶
Testing Environment to test your module
Use this environment to test new functions and the whole module integration in general
Frontend: https://app.tes-bayer.hortiview.com/CommonData: https://app-hv-c-commondata-tes-weu-001.azurewebsites.netModuleApi: https://app-hv-c-moduleapi-tes-weu-001.azurewebsites.net
Demo¶
Demo Environment as staging environment for testing phase
Use this environment to publish your module for testers of hortiview
Frontend: https://app.dem-bayer.hortiview.com/CommonData: https://app-hv-c-commondata-dem-weu-001.azurewebsites.netModuleApi: https://app-hv-c-moduleapi-dem-weu-001.azurewebsites.net
Production¶
Full production environment
Modules in this environment can be consumed by real users
Frontend: https://app.hortiview.com/CommonData: https://app-hv-c-commondata-prod-weu-001.azurewebsites.netModuleApi: https://app-hv-c-moduleapi-prod-weu-001.azurewebsites.net
url-pattern slightly different
Please be aware that the frontend is different to the other environments and the [ENVIRONMENT]-part is "prod" and NOT "pro"