ERPNext customizations, saved to Git
Built in the app. Saved into your code.
Custom Migrator lists the settings your team changed on this site that are not yet in your app’s code on GitHub. Tick the ones that should go live, and it writes them into your app, pushes them to a branch of their own and offers you the pull request.
Built in the app. Saved into your code.
Custom Migrator lists the settings your team changed on this site that are not yet in your app’s code on GitHub. Tick what should go live and it writes them into your app and pushes them to a branch of their own.
- Change detection: Anything already merged into your main branch is hidden, along with everything ERPNext and your other apps ship themselves. What is left is your team’s work.
- Export preview: Each item is marked new or changed, so you know exactly what the push will contain.
- Config as code: The changes are written into your app as files your repository already understands, so the next deployment applies them to any site you run.
- Pull request workflow: Each export goes up on a fresh branch of its own, and one click opens the pull request with the message and description already drafted. Tag a release too if you want one. Nobody else’s half-finished work comes along with it.
WHAT IT DOES
What it moves. The changes teams actually make.
The fields your team added, written into your app one file per form.
Renamed labels, new defaults, and fields your team hid or made required.
The code your team wrote to check or change records, saved into your app so every site gets it.
The stages a document moves through, and the states that go with them.
Email and in-app alerts, with the conditions that decide when they fire.
Whole new record types and other kinds of change can be switched on in settings.
FEATURES
Around every export. Clean, traceable, secure.
With HydraAI on your site, the commit message and pull request description are written for you from what actually changed. You can edit both before pushing.
The same change always produces the same file, without timestamps or staff email addresses, so a pull request shows only what really changed.
Every export, push and pull request is recorded with who, when, branch and commit. Entries can’t be edited afterwards.
Your GitHub token is stored encrypted and never appears in URLs, Git settings or logs. People can publish without ever seeing it.
COMPARED
Better than exporting by hand and hoping.
| Exporting by hand | Custom Migrator | |
|---|---|---|
| What gets exported | Everything, including records ERPNext ships itself | Only what is not in your main branch yet |
| Seeing the change | Read the raw files yourself | Each item marked new or changed before anything is written |
| Teammates’ work | Whatever happens to be on your machine | A fresh branch, holding only what you picked |
| Getting it reviewed | Commit and push by hand | Pushed to a branch, pull request one click away |
| Breaking the next deployment | You find out on the live site | The changes that would break it are stopped first |
Questions
Do I need Hydra to use it?
No. Anyone who administers the site can use it. With Hydra installed it also drafts the commit message and pull request description; without it you get a plain summary you can edit.
Where do the changes go?
Into the app you choose, on a branch of its own in your GitHub repository, ready to open as a pull request.
How do they reach the live site?
Merge the pull request. Espresso builds and deploys it and the changes are applied. Any other setup that deploys from GitHub works too.
Is my GitHub token safe?
It is stored as a password and never written into your repository’s settings or the addresses it pushes to.