Dev and Test/QA setup
Greetings
Just after some general comments or advise here…
We are wanting to set up new Development, Test/QA and Production servers for our Geocortex environments. To save on server maintenance costs we are considering the possibility of running the Development and Test/QA environments on the one server by installing two named instances, for example:
C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Development\Rest Elements
AND
C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\QA\Rest Elements
This way we can do our development “copy” the site over to the QA instance for user testing, and then continue development without affecting the test environment.
We have just set up a new virtual server with the specs:
OS Windows Server 2012
Processors 4
RAM 8GB
Disk Space C:\ 100GB
Is this plan feasible? Does anyone else operate like this? And if so, have you experienced any issues with this type of setup? OR … are will still better having totally separate Dev and QA servers?
Any thoughts would be greatly appreciated.
Cheers
Chris
-
I'm using the same specs except I have 16GB of RAM. This is only because my Geocortex Server is also my ArcGIS Server.
I used named instances for my test and production environments on the same server. I've found it to be very useful. To move an app from test to production, all I have to do is copy the config to the prod instance and then update the URL in my inetpub directory to point the app to the new version and complete the upgrade.
Disclaimer: I'm running Geocortex apps for a city government with about 400 employees and a resident population of about 78,000. So if the server goes down for some reason, we can just send an email saying it's down and we're working on it. If I was at a larger or private organization, then I would probably follow the separate server methodology so I had failover options.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar