- #INSTALLATION STAGING AREA HOW TO#
- #INSTALLATION STAGING AREA UPDATE#
- #INSTALLATION STAGING AREA PRO#
#INSTALLATION STAGING AREA HOW TO#
The following procedure shows how to set up a subdomain using cPanel. If you want to access your staging site as a subdomain (), you will have to configure the subdomain using your host’s control panel. If you’re going to use a subpath (), simply create a subdirectory within the main storage area for your site (e.g. Which option you choose is a matter of personal preference. The first thing to determine is if you want your staging site to reside within a subpath on your main site’s url or on a subdomain ( vs. You can use other plugins to do this or move the site manually.
#INSTALLATION STAGING AREA PRO#
The process makes use of the Duplicator Lite or Duplicator Pro plugins which can bundle up your site and move it to a new location.
It involves establishing a staging site, making changes on the site, then moving the changes back to your production site. What follows is a best practice for ongoing WordPress development. Steps for Creating a WordPress Staging Site However, if you’re running a web-based business, using a staging site is essential since any downtime or data loss on the live production site directly impacts your bottom line. Using a test site for a hobby website may or may not be worth the trouble. In this way, the production site is always protected from catastrophic mishaps. The idea is that you make all your significant changes and perform testing on the staging site, then move the changes over to your production site. The site is either a copy of an existing production site you want to change or is a fresh site you’d like to work on before implementing production.
What’s the alternative to performing all updates on the live site then? Simple: Create a clone – often called a staging site.Ī staging site, also known as a test or development site, is a duplicate WordPress site you use when implementing large scale or risky changes.
#INSTALLATION STAGING AREA UPDATE#
Perhaps it was a plugin update that blew up the site, or a theme overhaul that took a lot longer than anticipated, or something else equally catastrophic or annoying. When most people start working with WordPress they get accustomed to routinely implementing all their changes on their live production site.Īfter a period of time it often becomes apparent that performing all changes on the live site can cause problems.
0 kommentar(er)
