Cloud container
A container runs the editing application but also handles staying in sync with your remote repository and running your site (in development).
# Cloud architecture
The following diagram shows how the various pieces of the visual editor work together when not in local development mode.
# Container setup
The container goes through a specific lifecycle when it is created or restarted. This is the process:
- Clone the Git repository.
- Run
postGitCloneCommand
, if defined. - Run
preInstallCommand
, if defined. - Run
installCommand
. The default is eitheryarn
ornpm install
if the configuration property is undefined. - If the configured runnable directory (set in the visual editor settings) is not the same as the project’s root directory, then also install dependencies in the runnable directory. To review your runnable directory, go to .
- Run
postInstallCommand
, if defined. - Run
devCommand
, if defined. Otherwise, run the default command based onssgName
.
# Content update flow
The following diagram shows how content is updated when not in local development mode.
# Self-hosted container
Please contact us for details about on-premise and self hosting.
Did you find this doc useful?
Your feedback helps us improve our docs.