Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: Staging Environment

  1. #1
    arh is offline Junior Member
    Join Date
    Jun 2008
    Posts
    14

    Default Staging Environment

    Are there any issues to be aware of setting up a staging environment on the same server as the production enviornment.

    Ideally this would be on a separate server, but in our situation putting both a staging environment and production environment on the save server works best.

    Obviously, the database will be named differently. And the web site will be configured on a different IP/URL.

    We will use this technique to test store featues before putting them in production.

    We may use this technique to stage AspDotNetStoreFront version upgrades to test before going live with them.

    Just truing to head off potential problems with this setup before we proceed with it.

    Thanks in advance!

  2. #2
    Rex is offline Banned
    Join Date
    Nov 2007
    Posts
    561

    Default

    It should not be a problem unless your traffic volume is really high and the production site needs all the resources it can get.

    Make sure you use a separate Application Pool for each.