Strapi V4 Deployment: Blueprint sync failures from Render.com YAML

[Mic]

Hello,
Whenever we push from Strapi local (“sqlite3”: “5.0.2”) to production (Postgres), the content we added in production gets wiped out.

There are currently no Strapi V4 repos for Render.com so we copied the yaml file from this repo:
strapi-postgres-cloudinary/render.yaml at master · render-examples/strapi-postgres-cloudinary · GitHub

Then we added a disk to the yaml based on this article:

Render Deployment - Strapi Developer Docs

This didn’t add a disk so we added it manually in the admin panel and updated the yaml file. Note: there is also no GB: 1 option - it starts at GB: 10.

We continue to get a Blueprint sync failure everytime we push from the local file with this message:
" There were a few problems with your current render.yaml . No resources are being managed until they’re fixed."

This is what our yaml file looks like

Can anyone help determine what we’re missing in the yaml file? I know other folks are trying to deploy V4 as well so perhaps you have found a solution.

Many thanks,

[crcastle]

Hi- We have updated the Strapi example repos to v4.1.5, so please check those out.

Some specific things that may help you:

• I don’t see any problems with the format of the render.yaml you shared.
• Strapi now requires an APP_KEYS environment variable. Check out the render.yamls in our example repos for how to define this. You can set its value with generateValue: true. Then config/server.js needs to be updated to use this value like this strapi-postgres/server.js at master · render-examples/strapi-postgres · GitHub
• There is an outstanding issue in Strapi v4 that doesn’t allow the public directory to be changed from the default: Move public path config to server.js by petersg83 · Pull Request #12534 · strapi/strapi · GitHub. The issue has been merged but has not been released in a new Strapi version yet. This means media uploads will be lost on every deploy if you are not using the Cloudinary version example repo.
• If you are using Postgres for your production deploy, the content saved in there should not be wiped out on every deploy. If you are still having this problem, I’d suggest getting in touch with us at support@render.com so we can look at your specific DB and services.

-Chris