I am able to access login page. However, login fails; various 404s in javascript console (all are .css or .js ).
All the files in question are within /home/regularuser/frappe-bench/sites/assets
Are these files in the wrong location? Should I move them? Or point erpnext to this path? How?
Lack of proper documentation is a critical piece around here, there is an assumption that we all know the nuances of the different flavors of Linux which from my reading over the last few months many of us don’t, but we are learning …
I have installed this product over 50 times trying to get different features working that should have been working out of the box i.e. mail, bench updates, and now backup each time instructed to patch this or try that or the more frustrating statement - I can not duplicate the issue. In the last case that is probably true because the respondent inherently executes something but leaves it out of the discussion because its second nature to them and not us layman using the product.
All of this is an awful lot of work for a product where many of the users in HR are technically minded but not experts, and may not have an IT department, they are accountants and HR administrators, this is open source so some of this is a byproduct of the projects realm and the sweat equity we must all contribute.
In an effort to help here are some key things that need to be added to the how to:
CentOS 7 needs SELINUX changed to at least permissive for easy install to work as planed.
Assign passwords for root if not assigned and create Frappe user before easy install, they no longer give you password a file in ver7 and you need the password later on especially with sudo commands.
Learn git commands it is the baseline of this project and there are frequently patches pushed that are not thoroughly tested. You will see this when you go to do a bench update and it fails. Git stash and Git commit are your friends in this situation. You run them under the apps directory for each app i.e. /frapee-bench/apps/erpnext
Bench commands are a moving target, in the errors you will see a directive like “bench --upgrade will fix this” but when you go to run it or do a bench help you find it no longer exist. that is where the forums come in handy but make sure you change the sort to latest or the fix you try may make things worse because the code is always changing and not compatible with previous patches in many cases I have experienced.
If you find a doc helpful copy it down I was dependent on “change hostname” doc on GitHub in my many installs and the link has been stale and missing for well over a week now luckily I remembered most of the commands and new how to manually rename the files…
Hope some of this helps others and saves a bit of time and frustration the potential is great with this project if we all help…
I do have a running chart of what commands, what prerequisites, etc. I keep using, and tracking what’s working, so that I can repeat these steps on each new droplet I try.
Still, this is very frustrating
Even after reading through enough docs to go cross-eyed, I haven’t found where
I agree we really need to make this all more systematic i am finally getting comfortable with this but it has taken months and it really should not be this difficult.
…