Visual Editor /Cloud project /

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 Visual Editor work together in a cloud project.

# Container setup

The container goes through a specific lifecycle when it is created or restarted. This is the process:

  1. Clone the Git repository.
  2. Run postGitCloneCommand, if defined.
  3. Run preInstallCommand, if defined.
  4. Run installCommand. The default is either yarn or npm install if the configuration property is undefined.
  5. If the configured runnable directory (set in the project or visual editor settings) is not the same as the project’s root directory, then also install dependencies in the runnable directory.
  6. Run postInstallCommand, if defined.
  7. Run devCommand, if defined. Otherwise, run the default command based on ssgName.

Can’t find visual editor settings?

We’re rolling out new visual editor settings. If you can’t find your visual editor settings, go to

.

Or select the new settings icon next to your project name and choose Visual editor settings.

# Content update flow

The following diagram shows how content is updated in a cloud project.

# Self-hosted container

Please contact us for details about on-premise and self hosting.