staging vs production – what’s the difference
let’s get nerdy for a second, shall we? in development, the live site (what your customers use + visit) is called production. and a test site (one that your customers do not have access to) is called staging. just like staging a home, this is a great place for seeing what the final result could look like.
perks of not working in production
while it’s fun to be able to make changes to your WordPress pages + menu then instantly see those tweaks on your live site, it can be dangerous. the page + post editor features undo buttons + preview tools to help, but some themes turn the revisions option off completely. so not only could you accidentally delete an entire section of content + not be able to go back, you could remove opt-in code, delete a core theme template, or install a new plugin without realizing that it conflicts with two other plugins you use.
but it’s not just about avoiding disaster. the reason that i recommend staging sites to my clients is that it’s a great place to play. (in fact, they are sometimes called a sandbox environment, which always conjures up feelings of being playful for me.) you can rearrange your menu + sit with it for a few days before unveiling it to the world. you can set up new plugins to replace ones you aren’t happy with + test them thoroughly before letting your customers see the new version. and you can see what different images look like in your header or slider before putting them front + center on your site.
how to set up a staging site of your own
option #1 – manually clone your site
the reality is that a staging site is a clone of your live/production site. so you can clone your existing site (using a tool like BackupBuddy) + install it on your hosting account as a brand new WordPress install. that way you are free to make changes + putz around before making those same changes to your public site.
when i set up staging sites for clients, these are the steps i follow –
- clone existing site with BackupBuddy
- install clone on server (usually in a folder named “dev” or “staging”)
- password protect the site
- optional: install a plugin to connect the two sites for quickly transferring changes
because you are cloning the existing site, your login will be the same, unless you change it after installation to keep them separate.
option #2 – automatic staging sites with Flywheel
for all of my hosting clients (yup, tiny blue orange offers hosting now!) this option is automatic. Flywheel has staging sites — currently being beta tested, but i’ve been so happy with them — where it’s set up with a click of a button. once set up, you can play on your staging site + then transfer all changes to the live site by, again, clicking a button. how easy is that?
no matter what your WordPress hosting situation is, setting up a staging site is a great way to keep changes from frustrating customers when they don’t quite work, keep you from feeling fearful of making changes + updates, and adding a secure measure to your site upkeep process. so set some time in your calendar to create your very own staging environment before the year is up!