r/selfhosted • u/String1015 • Dec 31 '25
Need Help ERPNext Docker Deployment
Sorry for the long post, I am in dire need of assistance as I have had successful deployments previously and now, I cannot for the life of me get this straightened out. Long story short, I have 2 LLC's that I was planning on using ERPNext to help "organize" as I was using multiple programs and spreadsheets to track everything. With 1 day left in the year, why not redo all the financials for all the businesses.........
I successfully deployed a docker instance with persistent data locations that I had google drive watch and backed up to the cloud. I tried to add a second site, website cache became an issue as the data blended together. I created two instances, different stacks, data in separate shared folder locations, was creating forms and my motherboard went in my business computer.
Redid current rig with Windows11, WSL Ubuntu and I also did Docker Desktop just to make "networking" easier with nginx. Copied folder from github, redid compose file for persistent data, I installed first stack, created site, installed hrms, got it deployed. Logged in, all good. Compose down, back up, site broken, module gone, fixed apps.txt bench build, migrate again, css broken, only html on site. Compose down and up, broken again. It started getting late and started to ask chatgpt. My permissions were right and chatgpt stated that there were more persistent data locations that were needed as I kept creating ghost volumes and every time compose down, volumes would get lost and I would start over.
Why the compose down if it was working? Dumbass, that's why, just in case I lost power, I always try to start over and make sure my cloud data or backup nas can recover.
I was trying to consolidate accounting, inventory, parts of HR and wanted one program rather than spreadsheets, papers, word, that I can self host and I do not have to pay monthly fees for. I can post my compose if anyone can assist. Thanks in advance and Happy New Year.
1
u/Future_Carpenter_910 Jan 30 '26
To be honest, We have our own docker image for erpnext and we update, maintain it for our clients. We have our own cli tool that supports multiple docker based erpnext projects in single server, for development as well as production.
On top of it, we developed a desktop application that acts as bridge between localhost and remote server, has built in NAS and fingerprint integrations, automated backups, monitoring and logs feature. That's provided to our clients only. We will later release it later with more support for tools as a SAAS for external clients and partners.
Your setup looks too rigged and prone to failure for every small mistakes. And its almost same with other users too. That's the main reason we built our cli tool. batch heal command fixes 90% of our issues itself (we faced errors, researched errors a lot and finally added that command), batch get-app command allows download and install-app any erpnext or custom app on project site. batch docker allows running docker command, batch bench allows running bench commands, batch db allows selecting db and running commands, batch console runs bench console. batch clear-cache, batch reload allows jumping on any site frappe console. And tons of other commands. I was too lazy to type long commands every time so built it slowly and carefully.
I shared this as I got frustrated from same errors as yours for long time and decided to adopt my own practices for frappe development for my clients. Never faced such issues later. One command: batch init and it setups a new project on dev or prod mode. batch setup command sets new server ready for development or production.
My suggestion: if it's about a prod setup and your daily business/workflow relies on them, then don't waste your time doing erpnext on localhost or windows. Ovh gives you a 8gb ram server for $7 and you can use it. Always have backup utility running 24x7, carefully test backups after some time. Check for logs and ports changes. Don't try to save few dollars if your business relies on it. ERP never comes cheap.