We’re implementing Strapi in our company and we’re wondering which solution is best:
Solution 1:
- Isolated database;
- Git for versioning new schemas;
- Use remote Strapi for content management.
- Run strapi as “prod” in all environments (dev, staging, production).
Solution 2:
- Put the schemas in .gitignore and use git only for plugin and strapi version updates;
- Modify the schemas via content type builder directly in the remote UI on the server;
- Back up the server at all times so as not to lose the schemas.
Which workflow do you recommend and do you work with today?
This topic has been created from a Discord post (1268594747174420593) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord