Upgrading by replacing files and running migration

[yurikuzn]

An optional way to upgrade.

Steps:

1. Replace all app files with files with files from a new version package.
2. Run bin/command migrate. It will run needed prepare and after-upgrade scripts, run rebuild. The version parameter in config will be updated.

Supposed to be used in docker installations.

[RoSk0]

This is an awesome feature! Thank you.

One thing to consider though, related to the

The version parameter in config will be updated.

Secure platforms are enforcing read only root file system . This means that the script will fail when it will try to update the version in the config file in at the run time.

I'm not familiar with the details of the version number usage from the config file, but can suggest to either read thatvfrom the code base or update during container image build.

[yurikuzn]

I'm not sure we can do it. We already have the config which is not read only. We already have the version parameter in the config which is writable by the application. We have also a read-only default config and the actual version will be taken from there. The config will contain the previous version. Using the version from the config was the most simple solution I could come up with. It's supposed to work in both docker and non-docker environments. Just compares two version numbers and runs needed scripts based on it.

[tmachyshyn]

If we are talking about docker implementation, all core EspoCRM files will be added while image build. The directories as data (where the config is located) and custom will be mapped to the host.
While starting the container, the entrypoint script will check the version, and run the bin/command migrate in case it requires.