After you’re happy with how everything’s working on your dev server, it’s time to schedule your prod (production) upgrade.
We recommend scheduling a 2-hour maintenance window and notifying editors they’ll be locked out, via email or by sending a bulletin. Typically pulling an upgrade takes between 10–45 minutes, but having some cushion time is never a bad thing.
We also suggest notifying email@example.com when you’ve scheduled your upgrade window. This will help us keep an eye out in case you require any urgent support during that time.
SFTP into your prod server and lock out editors
Login to your prod site at /livewhale/?login (clicking “Click here if you have upgrade access” to bypass the lockout)
Once logged-in, visit /livewhale/?updates_pull
Double check that the page says “Production server:” and that you are pulling to your production site from your dev site.
Scroll to the bottom of this page and click “Run this update”
After clicking, wait a minute for the upgrade to run. After you see “Upgrade is complete” or “Server is up-to-date” click the link provided to logout (or visit /livewhale/?logout).
Note: Some testers reported seeing a white screen here, indicating a server timeout. We’re working on that, but if you see it, simply wait 15–30 seconds and refresh and the upgrade should continue normally.
Log back in to trigger any database upgrades (this may take a few minutes the first time you login after an upgrade)
Go back to /livewhale/?updates_pull to double-check that there are no remaining files to pull—if any files are listed, go back to Step 5. If it says “Server is up-to-date,” continue to Step 9.
Using SFTP, copy to prod any changes to /_ingredients or /livewhale/config/ that you made on dev during your testing.
Once you login and confirm the upgrade has completed, you can remove the editor lockout
You’re done! Thanks for using the latest version of LiveWhale, and feel free to drop us a note to let us know how everything went for you. We welcome your feedback on the upgrade process.