We have a project that uses a few modules from ERPNext and we could choose to make a few customisations to what we use. But when a new version of ERPNext is available from the Github repo, how do we update or upgrade?
How much time does it take to finish the update? Is it safe to test the new update on a development environment before updating it on the production environment?
Does it overwrite any customisations we make to some of the inbuilt modules present in ERPNext such as CRM or Stock? If then, how do we manage to install the new update as well as keep up the customisations?
And how often do we need to follow a maintenance schedule?
To update or update ERPNext, you can follow the steps mentioned in the official documentation.
This typically involves pulling the latest code from the ERPNext GitHub repository, updating the Python and Node.js dependencies, and running a migration script to update the database schema.
The time it takes to complete the upgrade may vary depending on the size of your database and any customizations you have made.
It’s generally a good idea to test a new update in a development environment before updating a production environment to make sure everything works as expected.
When you upgrade ERPNext, you can potentially overwrite any customizations you’ve made to built-in modules like CRM or Stock. To manage this, you should use a version control system like Git to track your changes and merge them with updated code.
The ERPNext documentation has a section on managing customizations during an upgrade.
As for the maintenance schedule, it’s a good idea to keep your ERPNext installation up to date with the latest security patches and bug fixes. You should also back up your database regularly to prevent data loss in the event of a failure.
How often you should follow a maintenance schedule depends on your use case and specific needs, but it is generally recommended to schedule regular maintenance at least once a month.