Tweet
We have one Valence data library and three HTTP servers, one for development, one for test and one for production.
The only reason we have three HTTP servers is because we have an environment variable (BM_HTML_PATH) defined in each to point to the different locations of our HTML source for each environment.
This environment variable is then used as part of the option definition to pick up the correct HTML for the selected environment, the HTML file to Initialize will be set to [BM_HTML_PATH]/ppe-request/current-user.htm, for example.
If up to five paths could be defined against environments and then used in options definitions (CLIENT_PATH_1, CLIENT_PATH_2, etc.) we would not need three HTTP servers, only one.
In the future, you could also consider defining which environments an options belongs to. Therefore when an option is being developed, you would only allow it to be part of the development environments. When user testing is taking place, allow it to be part of the QA environments. Then finally allow it to be part of all environments.
If both the above where implemented, you may find most clients could run one data library and one HTTP server.
The only reason we have three HTTP servers is because we have an environment variable (BM_HTML_PATH) defined in each to point to the different locations of our HTML source for each environment.
This environment variable is then used as part of the option definition to pick up the correct HTML for the selected environment, the HTML file to Initialize will be set to [BM_HTML_PATH]/ppe-request/current-user.htm, for example.
If up to five paths could be defined against environments and then used in options definitions (CLIENT_PATH_1, CLIENT_PATH_2, etc.) we would not need three HTTP servers, only one.
In the future, you could also consider defining which environments an options belongs to. Therefore when an option is being developed, you would only allow it to be part of the development environments. When user testing is taking place, allow it to be part of the QA environments. Then finally allow it to be part of all environments.
If both the above where implemented, you may find most clients could run one data library and one HTTP server.
Comment