<p>If it's a new environment with your staging database, then run this on your new production environment:</p>
<p><code>./craft project-config/rebuild</code></p>
<p>This will force-dump the config into the project-config YAML files from scratch, and include any small changes that might have happened to make way for the new environment, including pesky caches.</p>

CC BY-SA 4.0
2020-12-18T09:14:28.227Z
Thanks very much. I ended up creating a new folder on the server and deploying to that instead. Just out of curiosity would doing that on production cause the yaml to be different to whats in git?
MartinD
CC BY-SA 4.0
2020-12-18T20:49:09.897Z
It all depends on how out of sync they ended up getting, but yes, it's possible. Any edits where a yaml file is removed, if your git re-adds the file and you `apply` them, the deleted content reappears. I've learned to use the database as the source of truth, not the yaml files.
Tammy Shipps
CC BY-SA 4.0
2020-12-16T22:36:15.333Z
2020-12-16T22:36:15.333Z
Tammy Shipps
<p>Deploying on production is giving me this error.</p>
<p>Applying changes from your project config files ... No site settings exist for section 20</p>
<p>Deploying to stage is working no problem. Production isn't live yet. It uses the same database copied from stage.</p>
<p>Any ideas?</p>

<deployment><project.yaml>
Applying changes from your project config files ... No site settings exist for section 20
# Applying changes from your project config files ... No site settings exist for section 20

(Asked by: username_0 on 2020-12-15)

Deploying on production is giving me this error.

Applying changes from your project config files ... No site settings exist for section 20

Deploying to stage is working no problem. Production isn't live yet. It uses the same database copied from stage.

Any ideas?

**Tags:** deployment, project.yaml

---

## 1 answers

### Answer by username_1 on 2020-12-16. Score: 3

If it's a new environment with your staging database, then run this on your new production environment:

`./craft project-config/rebuild`

This will force-dump the config into the project-config YAML files from scratch, and include any small changes that might have happened to make way for the new environment, including pesky caches.

> **Comments:**
> **username_0**: Thanks very much. I ended up creating a new folder on the server and deploying to that instead. Just out of curiosity would doing that on production cause the yaml to be different to whats in git?  
> **username_1**: It all depends on how out of sync they ended up getting, but yes, it's possible. Any edits where a yaml file is removed, if your git re-adds the file and you `apply` them, the deleted content reappears. I've learned to use the database as the source of truth, not the yaml files.  

---

