GridPane includes the option to easily create a staging website for your primary website, and/or turn a staging website on or off at any point.
Inside your account you can push your live website to your staging site (or vice versa) anytime with just a few clicks.
Troubleshooting tip 1: At the time of writing, our current backup system runs backups every hour on the hour. While this is running, staging pushes will not be able to take place. Our new system will remove this problem, but for now please note that if a push does fail and it's near the hour, it may be because backups are locked.
Troubleshooting tip 2: If you're finding that your staging push is hanging (nothings happening), it may be due to your backup token being out-of-sync. Head to your servers page in your account and hit the refresh button under "Status" to sync things up, and then try your push again.
About Staging Sites
Staging sites are an excellent way for you to develop and test a clone of your production website directly on your production server.
These are created with the popular "Force Login" plugin installed and active, so you won't be able to view them without first signing in, and they also include the following rule to prevent search engines from indexing them and potentially causing duplicate content issues/penalties:
X-Robots-Tag: noindex, nofollow, nosnippet, noimageindex
Please note that if you're importing your website via a plugin and overwriting the database, then by default the force login plugin will no longer be active once the import has completed (unless you installed it on your site before migrating it in). This will also override the default login credentials.
Staging and Backups
Previously when pushing from live to staging or vice versa for the first time, it required a backup of both your live site and your staging site if one didn't already exist. This is no longer required, and is now taken care of automatically. If a backup fails, then the push process will cease to run, and exit.
You also now have the option to skip taking a backup when pushing from Live -> Staging.
For Staging -> Live pushes, a backup is mandatory, and will automatically take place.
Backups here are mandatory to prevent your sites being lost forever if you accidentally push the wrong way. The skip option above will only work when pushing to your staging sites, but please always proceed with caution, and run backups when you need to.
Pushing a Website from Staging -> Live or Vice Versa
Making a staging push is quick and simple.
Step 0. First, if it isn't already, toggle on the staging site for your website.
Step 1. Navigate to your staging page and locate your domains staging site.
If your staging site is brand new, first take a manual backup my clicking on the website name to open up the configuration modal, and then opening up the backups tab. Click "Backup Now". If your staging site isn't brand new, this may not be necessary.
Step 2. Choose your staging push option.
Click on the appropriate button for your push (live to staging or staging to live). Be sure to select the correct option so you don't overwrite the wrong website. This will open up a modal as shown below.
Choose your staging push option from the dropdown and click the "Push Live to Staging" / "Push Staging to Live" button
Step 3. If doing a partial database push, select your tables (not applicable for full pushes).
This is only applicable if you know what specific database tables you want to replace.
Once your push has completed you will see the following notifications and you can now check out the changes.
On completion, a full cache clear will take place on the new website so you should be able to see view the website correctly, without a pre-stored version showing in it's place via the cache.
If your staging push failed, you can check your log by clicking on the icon next to your staging site:
Here you can view the results of your push, and it will detail the reason it failed to go through: