config/sync system.site.yml

Curious have you used this on deployments? Seems the issue when using this config/sync is:

not sure if ignoring that single file would work in .dockerignore or how to best to handle using this build on local development as well as once deployed... obviously the uuid changes, not sure best way to handle for updating on a local, dev, prod setup for this code base.

Thoughts?

Start by examining config/sync/system.site.yml and how config/sync is handled during the image build and deployment. Compare the .dockerignore and local, development, and production workflows mentioned in the issue; done means establishing a consistent approach that avoids environment-specific UUID conflicts.

Written by the indexing model from the issue text.