Seems promising but installation is too complicated and stability is questionable
Thank you for your great work. However I have several comments regarding a new user trying to install and use ERPNEXT.
- micro server gen10
- SSD for server OS
- 2 HDDs RAID 1 for LXC containers
By the way: i tried LXD without success and gave up (instability when doing snapshots save/restore)
Server OS: archlinux
Containers: LXC with archlinux inside
Container Archlinux commands to install ERPNEXT (# means root, $ means user):
pacman -S mariadb redis python-pip python-setuptools wkhtmltopdf git npm cronie nginx
pip install -U pyOpenSSL
npm install -g yarn
Remark: Please see that we need to install pyOpenSSL and yarn to proceed during ERPNext installation (could be interesting to add it in the installation procedure)
mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
systemctl start mariadb
mysql -V ### Check that mariadb version is 10.1.34 due to a known bug - see ERPNext forum
character-set-client-handshake = FALSE
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
default-character-set = utf8mb4
systemctl start mariadb redis
systemctl enable cronie mariadb redis
$ git clone https://github.com/frappe/bench bench-repo
$ echo “export PATH=$HOME/.local/bin:$PATH” >> ~/.bashrc
$ pip install --user -e bench-repo
$ bench init frappe-bench && cd frappe-bench
$ bench get-app erpnext https://github.com/frappe/erpnext
$ systemctl status mariadb redis cronie # check that services are up and running before proceeding
$ bench new-site site1.local
$ bench --site site1.local install-app erpnext
$ bench use site1.local
$ bench start
Remark: it was necessary to use Python3 to end the installation procedure
- Maintenance and deployment
Regarding the previous install, you can see that i did not select any ERPNext versions.
As a company, i want to have a stable version installed. How do we do that ?
If we look at the github frappe/erpnext repository we can see that all the branches (more or less) do not success in the continuous integration process. Is this normal?
My point of view is that ERPNext team should:
- provide release and tell people on how to install it in an easy way (checking several platform and environments) The first impression always gives something important for user adoption
- provide stable fix on the release in order to prevent any major issue for a production env.
- offer a dev branch to test latest development
The main concern is that your communication is not clear, your procedure to switch from one version to another is not clear and more important it seems that you develop more new features than correcting bugs and improving first installation impression.
I am really convince that ERPNext is an interesting product but installation and upgrade is a nightmare!
- Finally, it seems that on the dev branch you can not do a “bench update” without doing a git stash in apps/frappe_io
This is definitely crazy, why don’t you fix that?
Industrial users need stability and confidence,
It took me 1 month to install the hardware, the server OS, the containers and finally ERPNext which is the hardest part.
If you think that I should have tried an Ubuntu installation, the answer is I did but without success. Virtual box is also not a solution (only for testing IMHO).
I do not think that my experience is special regarding industrial user needs but i can tell you that my my patience has been put to the test.
Continue your great job but please focus on installation, maintenance, update procedure and up to date documentation in order to have plenty of happy users.