tried frappe drive docker the other day … broken,
tried bare metal install app on an existing frappe server … broken.
tried frappe cloud drive version… same broken-ness…
what’s going on?
all kinds of console log errors. it can’t be me right? if I did the frappe cloud version and got the same results?
I am using Drive in a docker setup and it works well. I have no complaints from the users.
We all know it is not a Google Drive, but a perfect fit for an organization that wants to keep its documents (or customer documents) close and not in the public (whether for regulatory or security concerns).
Anyways, can you provide details?
What is the Drive App version that you used?
What are the Frappe and ERPNext versions that you used?
Which image of the Frappe Docker did you use?
What docker installation did you go for?
I personally use my own custom docker image.
https://hub.docker.com/r/knimer/erpnext
This image includes many apps in addition to the ERPNext and Frappe ones. This means you only need to run:
bench --site your.site.name install-app drive
then bench --site your.site.name migrate
to add the Drive App and allow the post-install scripts/logic to run.
Try this, and let me know. At least the mix of versions is working fine for me.
Given that the original Docker Image Containerfile does not include Drive. It does not including 2 Linux system packages that are needed by the Drive App. (Normal)
For the image I mentioned above, given that Drive App is included, so these 2 Linux packages are included as well.
So, the custom Containerfile used to build the above image adds these 2 Linux packages:
I did post an issue with screenshots on GitHub it looks like it’s starting to get resolved. there was all kinds of errors in console log and nav bar wasn’t showing on bare metal, docker version and even frappe cloud but they got that fixed for the most part now. there’s still an issue with creating folders not showing til you refresh the page as well as documents. folder uploads fail still. and there is an issue its complaining about invalid url structure for web socket in the console log still.