ERPNext - cost-effective ERP solution
Okay, here is the good news. Please try it out and let me know if it works.
If you're not ready to build the image yourself, you can simply install the image that I created.
cloudron install --image njsubedi/cloudron-erpnext -l erp.<yourdomain.tld>.
ErpNext v14 is now available on Cloudron. See the README file for usage instructions.
- ErpNext v14 - running on Frappe Framework v14
- HRMS Module - Includes HR and Payroll modules
- Plug n Play - Automatically configured to use the subdomain you install it on, no setup needed
- Independent - Does not depend on Cloudron Addons for redis, mysql or such
- Installs its own database servers, but data resides inside /app/data, so it gets backed-up, no not a big issue
- Hasn't been tested a lot, but it's working pretty fine
- Multi-tenancy isn't set up, even though that's pretty trivial to do
Good to know
- After installation, look into
/app/datafolder using cloudron's file manager for a file that ends with
- Raise issues on Github if you run into problems, not here.
You are a Free Software hero right there, @nj !
Can somebody review the code?
@girish what else needs to be done so that it can be released as an unstable app in the store?
- only dev branch for hrms and payment module and no release (yes I'm aware that only the dev branch exists - this has to be adressed in the future)
- does not use Cloudrons Redis
- Will some of the database mitigations break the insallation in the future?
I will wait until the unstable release at the Cloudron App Store and start testing then
I’ve added Cloudron LDAP support. I’ll push the changes this evening.
I think I can do Cloudron redis too. Looks doable.
I think after the default site is created, I can dump the db and import that to cloudron MySQL, but still ErpNext devs recommend Mariadb support only, and it needs the database name to be the same as the db user name. Unless there’s support from Cloudron devs, it’s a blocker. But I have set db path to be inside /app/data, so backup is not an issue. Also tried migration and backup-restore, which worked fine.
Since I’m actively using it at my company I’ll keep supporting this app. Also Keycloak, Outline and Odoo.
I was able to successfully build and run the package nj published on github for the last couple of months.
It seems to work fine, though I have not had a chance to evaluate how the upgrade and backup/restore process goes (I still have concerns about how it would interact with cloudron long-term), and I've only just started setup for a few modules.
From my (limited) experience, if you want to use ERPNext, be prepared for an extended commissioning phase. The product is both wide and deep, you will be taking considerable time to learn the ERPNext system and configuring it to work with your business process. ERPNext is moderately opinionated on how things should work, an approach I generally appreciate, but I found integration to be a big task as it pushed me to shift my expectation on how things should be organized to the "ERPNext-way". To be fair, this could be as much my ignorance of ERP systems in general as ERPNext's particular obtuseness, but I suspect the truth is that any large integrated bookkeeping system will exhibit similar commissioning/integration difficulties by the very nature of its size and scope.
I don't mean to push anyone away from the product, just to lay out realistic expectations of how much effort it will take on your part to integrate a product of this scope into your business.
I have published an update for ERPNext on Github - cloudron-erpnext-v0.20.0 This version is stable, but has breaking changes from the first release, so instead of updating you'll need to export and re-import the documents manually. This won't be necessary from future updates.
- Built on the base image version 4.0 (Ubuntu 22.04), so the source code is much lesser and simpler.
- Uses Cloudron's redis service, as requested by one of the members.
- The webserver and supervisor run as a normal (non-root) user so it's a bit more secure
- Existing apps (frappe, erpnext) etc can be updated easily from the terminal. There will be no need to update this app anymore from this point onward.
- New apps (like hrms, frappedesk) can also be added or removed easily.
- LDAP Settings can be configured if needed using the included script.
- There's preliminary support for multi-site setup.
I request someone to test this package and give some feedback. Thank you.
If building the app sounds complex, you can simply use the existing package by running
cloudron install --image njsubedi/cloudron-erpnext:20230104-200417-70210de70 -l erp.your-domain.tld
Note: the latest image can be found at https://hub.docker.com/r/njsubedi/cloudron-erpnext/tags . Replace
20230104-200417-70210de70with the latest tag.