Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- Why Remote-Live Staging in Liferay SaaS not required?
Environment
- Liferay SaaS
Resolution
Remote-Live Staging is not required in a setup like cloud environments. The reason behind the same of the below parameters:
- For a standard Production HA environment, an additional Liferay instance (or "node") is required with the intention of using it as a Staging node. This is possible in on-premise environments but not possible in Liferay Experience Cloud. This is due to there's no way of guaranteeing that a single container lives long enough for completing the Publishing process. Containers come and go, so this is simply not doable as a limitation with containers.
- All development modifications would be done on UAT and then promoted to both Production and Staging. All content contributions would be done on the Staging environment and then published to the Live Production environment. For this to work, all communications between Staging and Live environments would need to be routed through the public internet using public URLs, as the environment resides in separate private virtual networks and can not reach one from another.
Instead, Local-Live Staging can be used in which the staging and live servers are the same but the changes would reflect to the end-users only when the changes have been published by the administrator.