Liferay Local Live Vs Remote Live Staging
September 23, 2016
Local Live Staging and Remote Live Staging are two approaches used to prepare and review changes before publishing them to a live site. Both serve the same goal but work in very different ways. Local Live Staging keeps everything on the same server, which makes setup simple and publishing faster. Remote Live Staging separates the staging and live environments across two servers, giving you more control and stronger isolation. Knowing how each option handles content, performance and deployment can help you choose the setup that matches your team’s workflow and the level of safety you need during updates.
| |
Local Live Staging |
Remote Live Staging |
| Server |
With Local Live staging, both your staging environment and your live environment are hosted on the same server. |
With Remote Live staging, your staging environment and your live environment are hosted on the different servers. |
| After enabling staging |
When Local Live staging is enabled for a site, a clone of the site is created containing copies of all of the site’s existing pages. Portlet data is also copied, depending on which portlets are selected when staging is enabled. The cloned site becomes the staging environment and the original site becomes the live environment. |
When Remote Live staging is enabled for a site, a connection is established between the current site and another site on a remote Liferay server. The remote site becomes the live environment and the current site becomes the staging environment. |
| Time requires to publish changes |
Local Live staging allows you to publish site changes very quickly, since the staged and live environments are on the same server |
Remote Live staging , It will take comparatively more time to publish site changes, since the staged and live environments are on the different servers. |
| Staged content |
The staged content is stored in the same database as the production content, the content isn’t as well protected or backed up as with Remote Live staging. Also, you can’t install new versions of portlets for testing purposes in a Local Live staging environment since only one version of a portlet can be installed at any given time on a single Liferay server. |
Your staging and live environments are hosted on separate servers. This allows you to deploy new versions of portlets and content to your staging environment without worrying about interfering with your live environment. |
| Undeploy the portlet |
Since the portlet data are same for both staging and live environment, if portlet is undeployed from server, then portlet will be no longer available in both staging and live environment. |
If you undeploy portlet from staging environment, live environment won’t be affected by doing this. |
Conclusion
Local Live Staging is a good fit when you want quick edits, fast publishing and minimal configuration. It’s efficient but offers less separation between staged and live content. Remote Live Staging takes more effort to set up but gives you cleaner isolation, safer deployments and better protection in case something goes wrong on the staging side. The right choice depends on your server setup, the size of your site and how comfortable you are managing updates in a shared or separated environment. If you understand the trade-offs, it becomes easier to pick the option that supports your long-term content and deployment strategy.
FAQs of Difference between Local Live Staging vs Remote Live Staging
1. What is the core difference between Local Live Staging and Remote Live Staging?
Local Live Staging runs both staging and live environments on a single server. Remote Live Staging separates them across two servers.
2. How does staging behave after it’s enabled?
Local Live Staging creates a clone of the site on the same server. Remote Live Staging links your current site to a remote server that becomes the live environment.
3. Which approach publishes changes faster?
Local Live Staging is faster because everything happens on one server. Remote Live Staging takes more time due to communication between two servers.
4. How is staged content stored in each setup?
Local Live Staging stores staged and live content in the same database. Remote Live Staging keeps them separate, giving you more protection and flexibility.
5. What happens if a portlet is undeployed?
In Local Live Staging, undeploying affects both staging and live environments. In Remote Live Staging, only staging is affected.
