Tweet
Hello,
I've been asked to assist a team in deploying an EspoCRM application into a cloud environment. I'm a fairly competent developer and have extensive experience deploying containerized applications, but EspoCRM is rather new for me and I'm looking to the community for help.
Our team would like to restrict development to a single "dev" instance of EspoCRM, and automate the synchronization to our "prod" instance. Does EspoCRM support a deployment scenario where users are not expected to duplicate their changes across instances?
From my own investigation, it appears that all (meta)data is stored in a single MySQL database; however, it's not clear to me how one could migrate the "dev" model/schema changes to "prod" without also copying all of the data over as well.
Thanks,
Chris​
I've been asked to assist a team in deploying an EspoCRM application into a cloud environment. I'm a fairly competent developer and have extensive experience deploying containerized applications, but EspoCRM is rather new for me and I'm looking to the community for help.
Our team would like to restrict development to a single "dev" instance of EspoCRM, and automate the synchronization to our "prod" instance. Does EspoCRM support a deployment scenario where users are not expected to duplicate their changes across instances?
From my own investigation, it appears that all (meta)data is stored in a single MySQL database; however, it's not clear to me how one could migrate the "dev" model/schema changes to "prod" without also copying all of the data over as well.
Thanks,
Chris​