Talk:Staging site

This article was nominated for deletion on 8 August 2016. The result of the discussion was redirect to Deployment environment#Staging.

It would be nice if this had more technical details so you could use this page as a starting point for finding out more info about setting one up.

Actually, as I see it, the staging server is NOT the same as the development server. On a development server, you code, design, tweak, things, whereas the staging server is supposed to be as close to a mirror image of the production site as possible, to avoid last minute problems with sites not set up in a development configuration. —Preceding unsigned comment added by 82.238.217.133 (talk) 17:09, 25 September 2007 (UTC)[reply]

Theoretically, the cycle would be dev->testing->staging->production, I think. Many frameworks include testing modes, so dev & testing can occur side by side. Staging would then be used for tests that can't easily be automated (acceptance testing? definitely usability testing). I'm not really sure about the distinction between testing and staging, though. Automated tests are normally fast enough to be part of the development process (either via continuous integration on a centralized VCS server or locally in the developer's own testing environment). The "mimicking the production environment" criterion should be fulfilled for most kinds of (non-automated) testing anyway, so that makes the staging definition a bit blurry. -- 78.35.115.245 (talk) 01:33, 31 January 2011 (UTC)[reply]