ERPNext - cost-effective ERP solution
-
Trailer
You know what's disappointing? I started packaging ERPNext for the HR module. Unfortunately, the HR Module is not available after installation. Now I'm here thinking where the hell it go, and why I spent weeks packaging something that doesn't have the particular module I was looking for.
Update: Looks like
version-14of ERPNext does not have HR module. Onlyversion-13has it.
Now packaging version 13.
@nj ERPNext 14 also have an LMS, right?
-
@nj ERPNext 14 also have an LMS, right?
@mdreira said in ERPNext - cost-effective ERP solution:
@nj ERPNext 14 also have an LMS, right?
Seem like yes, indeed, as it is written on the quoted page. And it seems to be very powerful as well.
Ignorance is not an excuse anymore!
https://AutomateKit.com -
@mdreira said in ERPNext - cost-effective ERP solution:
@nj ERPNext 14 also have an LMS, right?
Seem like yes, indeed, as it is written on the quoted page. And it seems to be very powerful as well.
After reviewing Odoo and Flectra, in their community and enterprise versions, I think that ERPNext is a very good option because it is 100% free software.
And it has a lot of features.
As @nebulon says, it is a cost-effective ERP solution.
-
@mdreira The big gotchya with Odoo is that the most useful part of it, the Studio addon, is not in the community edition.
With ERPNext, their equivalent no-code custom data model builder is included.
-
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.
Features
- 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
Gotchas
- 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-credential.txt. - Raise issues on Github if you run into problems, not here.
-
Wow, this app wishlist post started at 2018…
-
@mdreira Yeahhh...all good things take time, plus ERP next at the time was not what it is now lol but that's even more reason to get it onboarded now =]
@plusone-nick I'm hoping the Cloudron team will support to include this formally in Cloudron soon. There might be some hindrances, but I think it should work relatively fine now, right?
-
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.tldNote: the latest image can be found at https://hub.docker.com/r/njsubedi/cloudron-erpnext/tags . Replace
20230104-200417-70210de70with the latest tag.Founder / Coder • My Apps
-
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.tldNote: the latest image can be found at https://hub.docker.com/r/njsubedi/cloudron-erpnext/tags . Replace
20230104-200417-70210de70with the latest tag. -
@jdaviescoates I doubt that because of a few reasons.
-
ERPNext cannot use the MySQL addon because it needs MariaDB and needs to have exact same name for database username and the database name (eg. db_name and db_username must be same),
-
ERPNext cannot use the Postgrest addon because it needs access to the database root user's password, which seems impossible to grant. There might be a possibility if that particular user had permissions to create new databases and user, which isn't possible right now.
-
A separate MariaDB service is running inside the container. the database files are stored at
/app/dataso they can be backed up. This might not be a good idea but many apps that use file-based database are already using this so this might not be an issue. -
The frappe-bench folder is huge (~1GB) and needs to be writable at runtime. Hence the backup size grows fast.
If there's no problem running an extra background process for mariadb, and storing the data in /app/data folder, I think the team can look into packaging it. Good thing is this app doesn't need regular update as you can run
bench updatecommand to automatically update the Frappe framework and apps like Erpnext.Founder / Coder • My Apps
-
-
@jdaviescoates I doubt that because of a few reasons.
-
ERPNext cannot use the MySQL addon because it needs MariaDB and needs to have exact same name for database username and the database name (eg. db_name and db_username must be same),
-
ERPNext cannot use the Postgrest addon because it needs access to the database root user's password, which seems impossible to grant. There might be a possibility if that particular user had permissions to create new databases and user, which isn't possible right now.
-
A separate MariaDB service is running inside the container. the database files are stored at
/app/dataso they can be backed up. This might not be a good idea but many apps that use file-based database are already using this so this might not be an issue. -
The frappe-bench folder is huge (~1GB) and needs to be writable at runtime. Hence the backup size grows fast.
If there's no problem running an extra background process for mariadb, and storing the data in /app/data folder, I think the team can look into packaging it. Good thing is this app doesn't need regular update as you can run
bench updatecommand to automatically update the Frappe framework and apps like Erpnext. -
-
@jdaviescoates I doubt that because of a few reasons.
-
ERPNext cannot use the MySQL addon because it needs MariaDB and needs to have exact same name for database username and the database name (eg. db_name and db_username must be same),
-
ERPNext cannot use the Postgrest addon because it needs access to the database root user's password, which seems impossible to grant. There might be a possibility if that particular user had permissions to create new databases and user, which isn't possible right now.
-
A separate MariaDB service is running inside the container. the database files are stored at
/app/dataso they can be backed up. This might not be a good idea but many apps that use file-based database are already using this so this might not be an issue. -
The frappe-bench folder is huge (~1GB) and needs to be writable at runtime. Hence the backup size grows fast.
If there's no problem running an extra background process for mariadb, and storing the data in /app/data folder, I think the team can look into packaging it. Good thing is this app doesn't need regular update as you can run
bench updatecommand to automatically update the Frappe framework and apps like Erpnext.@nj
What you suggested is actually really hard to backup.
And it's not the best to have too many process in the same container.
Docker container differentiate from other container tecnologie to be single service container, even if they support multi services is not the best, especially for db.
Due to resources management especially. -
-
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.tldNote: the latest image can be found at https://hub.docker.com/r/njsubedi/cloudron-erpnext/tags . Replace
20230104-200417-70210de70with the latest tag.@nj hey thanks for doing god works, i tested it and works really well.
but i running to some problem when adding another erpnext site using different domain, seeing this message when visiting the urlYou are seeing this page because the DNS record of erp.redacted.com is set to this server's IP but Cloudron has no app configured for this domain.i'm running this command succesfully in the terminal
gosu cloudron bench config dns_multitenant on gosu cloudron bench new-site erp.redacted.comi'm sorry if this sound stupid, im new to cloudron
-
@jdaviescoates I doubt that because of a few reasons.
-
ERPNext cannot use the MySQL addon because it needs MariaDB and needs to have exact same name for database username and the database name (eg. db_name and db_username must be same),
-
ERPNext cannot use the Postgrest addon because it needs access to the database root user's password, which seems impossible to grant. There might be a possibility if that particular user had permissions to create new databases and user, which isn't possible right now.
-
A separate MariaDB service is running inside the container. the database files are stored at
/app/dataso they can be backed up. This might not be a good idea but many apps that use file-based database are already using this so this might not be an issue. -
The frappe-bench folder is huge (~1GB) and needs to be writable at runtime. Hence the backup size grows fast.
If there's no problem running an extra background process for mariadb, and storing the data in /app/data folder, I think the team can look into packaging it. Good thing is this app doesn't need regular update as you can run
bench updatecommand to automatically update the Frappe framework and apps like Erpnext.@nj thanks for comments.
Strikes me that someone needs to be brave and just say 'ERPNext will not be packaged for Cloudron', as much in fairness to those who are really keen on it so they know it won't happen and they can look to self-host on a different VPS.
I don't have a dog in the fight, just trying to improve clarity and reduce "app anxiety".
There is no mechanism to "close" an entry in AppWIshlist. Maybe there needs to be one?
Of course, if I am wrong, that's fine, the exploration can continue.
-
-
@nj thanks for comments.
Strikes me that someone needs to be brave and just say 'ERPNext will not be packaged for Cloudron', as much in fairness to those who are really keen on it so they know it won't happen and they can look to self-host on a different VPS.
I don't have a dog in the fight, just trying to improve clarity and reduce "app anxiety".
There is no mechanism to "close" an entry in AppWIshlist. Maybe there needs to be one?
Of course, if I am wrong, that's fine, the exploration can continue.
@timconsidine you can of course install ERPNext at Cloudron with the package provided by @nj
It just needs some extra care and is not listed at the app store. Cloudron was always very open to custom package development and will push its efforts even further in the future.There is no need to close the listing at the App Wishlist since there is still high demand for ERPNext and maybe at some point the app store will open up to list community maintained packages.
