I have not tried to reinstall it recently, but if the case and installation procedure to get it running is the same as the one I mention in this thread it is not worth it.
You see, to get it running, there are three main pain points, the last of which results in a broken system:
- NodeJS PPA
- Lack of ARM MariaDB, working around Ubuntu/Debian repo’s MariaDB default behavior
-
chromedriver@2.37.0dependency in the stable branch (as of when the post was last updated, I don’t know if the dependency remains with later or latest stable releases)
The NodeJS and MariaDB workarounds I’ve detailed, but the workaround for the chromedriver thing (I don’t recall which component depended on it and its usage in the project) means running a Frankenstein monster setup of Frappe and ERPNext. The Frappe installed will be stable, but the ERPN will be of the development branch. The resulting database structure is so fragile, it will break if you were to attempt to bench update anything. In fact, attempting to do just that resulted in me creating this post: Recover item master, purchase and sales invoices from SQL dump
Now, however, the Frappe projects README mentions RPi in installation requirements, so I want to give it a try again, and see if they can add NodeJS’ ARM repo automatically, use distributor’s MariaDB package and finally done away with the chromedriver dependency.