[wp-trac] [WordPress Trac] #12865: Better support for beta/staging
WordPress Trac
wp-trac at lists.automattic.com
Wed Apr 14 07:27:58 UTC 2010
#12865: Better support for beta/staging
--------------------------------------------------------------------------------------+
Reporter: mnolin | Owner:
Type: feature request | Status: reopened
Priority: normal | Milestone: Future Release
Component: General | Version:
Severity: normal | Resolution:
Keywords: beta, staging, development, ease of development, development, migration, |
--------------------------------------------------------------------------------------+
Changes (by hakre):
* status: closed => reopened
* resolution: invalid =>
* milestone: => Future Release
Comment:
Well it's not just an idea, it's a valid use-case scenario that is pretty
well known at least by senior webapp developers.
I promote to document a standard staging scenario for wordpress and then
to provide the manual steps to do it. After some iterations it should be
clear which steps needs to be performed for staging.
The next step is to implement/automate that. Within or after this stage it
might be wise that core-code provides some actions so that plugins and
themes can reflect a change of the domain name for example.
I have moved some sites, I think the two most imporant parts are:
- change of a domain name
- database versioning
Better fitting then the ideas forum is a codex page for that documentation
process. As a start I created a page: [http://codex.wordpress.org/Staging
Staging in the Wordpress Codex] which already contains all basic
information and related links.
I reopened this ticket because I think this is interesting for some
serious administrators and developers.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12865#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list