Deployment strategies for environments (dev->staging->prod)

Hey guys,

I’m currently setting up a new project and we think about the way how to deploy changes across different environments. We will have the AWS S3 Plugin integrated to outsource media into an extra storage. The database will be postgresql and might be the same db instance as for the backend. (Would you rather separate the DB into an own instance?)

Is there a best practice when hosting the environments of how to structure the deployment process?

We thought about using the import-export (Import Export Entries | Strapi Market) to make changes in development and then run an export that will then be imported into the staging environment. We were thinking about using the same aws s3 instance across all environments.

Do you see any issues regarding that setup and deployment process? Or any thoughts about thinks we should consider? Hope to find some strapi ninja that can challenge our idea.

This topic has been created from a Discord post (1260701838634909818) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

Best practice - Deployment strategy for non-cloud environments (dev->staging->prod)

Best practice - Deployment strategy for non-cloud/self-hosted environments (dev->staging->prod)