Apply on other sites

Custom Migrator's job ends at the pull request. After it's merged, the customizations reach another site when that site updates the app and runs bench migrate, the same way any app update does.

On Espresso Cloud

Merging the pull request into the branch a site deploys from starts a new build and deploy. bench migrate runs as part of it.

On your own server

On each site's bench:

cd apps/acme_erp && git pull && cd ../..
bench --site your-site migrate

The app must be installed on every site that should receive the changes. Custom Migrator itself doesn't need to be.

Deleting and undoing

• Deletions don't travel. Deleting a custom field on your development site doesn't remove it from the app's files, and removing it from the files doesn't delete it on other sites. Delete it on each site by hand.
• There's no undo. Reverting the pull request removes the files from Git, but anything bench migrate already created on a site stays there.

Next

• Troubleshooting