Config strategies for deploying content from staging to live

Created on 28 April 2025, 4 days ago

Problem/Motivation

I'm curious what other people have figured out for managing config on a site that's using ES to deploy content between environments.

In my case, I have two environments, staging and live. Entities are pulled from staging into live.

Both environments are the same site, but I'd rather not have the ES server enabled on the live site. So I'm doing the following:

- the ES module is in the main branch
- configuration for the ES server is on a 'content-staging' branch, which is deployed on the staging server
- configuration for the ES client is on the main branch, which means it's also on the staging server.

Is there an easier way to do this? Am I overthinking this?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Version

4.0

Component

Miscellaneous

Created by

🇬🇧United Kingdom joachim

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @joachim
  • 🇬🇧United Kingdom joachim
  • 🇫🇷France Grimreaper France 🇫🇷

    Hi,

    I don't think this is an Entity Share problem :)

    I think it falls in the problem of any config you may want on an environment and not on another.

    Proposal 1:
    - use config_exclude_modules in settings.php to exclude all entity share modules from exported config
    - script the activation and configuration of Entity Share Client on live and Entity Share Server on staging
    - also with config overrides in settings.php with env variables if needed or it it helps

    Proposal 2:
    - use Config Split and create one split for live and one split for staging

    Proposal 3:
    - other workflow similar to the proposed ones above but with your favorite config tools

  • 🇬🇧United Kingdom joachim

    > I don't think this is an Entity Share problem :)

    Agreed :)

    I'm just curious what other people have come up with for managing this scenario.

Production build 0.71.5 2024