Installation instructions are outdated

My intention was not to get paid for the script that’s why i made it publicly available and I try to suggest it to anyone who is in need of installation guidance. I intend to continue to update it (so long as frappe remains truly free and open source which is now doubtful going by recent events). I am actually working on improvements to better handle logging so users can easily see errors if/when they occur. That update will be released soon.

Should you wish to show appreciation for my effort though, you can private message me and i’ll share info on how you can buy me coffee :wink:

2 Likes

I have a development background, but I am not a big fan of docker. It just kind of ‘moves’ the complexity without solving it

I installed the frappe framework on Ubuntu version 24 step by step (I used the online instructions I did not try flexy2ky’s script as I was not aware of it)

I did get it working but it took a long time and many times I got errors. Fortunately the error messages gave clues on how to solve.

what do you mean?

This has been implemented as part of the latest update pushed. Users are now given the option of installing ERPNext as well as HRMS. Other apps will be included in due course.

I disagree. Docker is much easier. What’s hard about it is learning yet another syntax. I gotta be in the mood for that. Put off learning Kubernetes for a year because “I didn’t feel like it” :stuck_out_tongue:

Essentially, docker is the install, and once you got the code(docker-compose file) you can set and forget with minor tweaks along the way.

Volumes and Db are mounted to the container. Or their own separate containers. Did you get a version that throws errors? No problem, delete that container and redownload the old version until erpnext folks iron out the issues.
Back up and running in as much time as it takes to nano docker-compose.yml and change erpnext version. 2 minutes.

On a manual install, if dependencies are updated along with the bork install… have fun fixing that. :stuck_out_tongue:

Not sure what to backup? nano docker compose and checkout volumes. Or just use the inbuilt backup tool.

Don’t get me wrong, this script from @flexy2ky is a masterpiece, but docker has it’s advantages beyond what a manual install can provide. Flexy’s script is easier than a docker install, but docker is better/easier than a manual install imo.

You make some really good points there Jake. I guess I stand by my ‘docker moves complexity rather than solves it’ statement, just because that’s what I’ve observed. But I am open minded on it.

I guess also even if you take moving complexity there is an argument that the complexity should be moved - from regular developers to infrastructure experts. Then us regular devs could simply run a line or two of script and have everything magically set up for us :slight_smile: