Hello Community,
I’m facing an issue with the deployment of a custom module on Frappe Cloud, and I need some guidance.
Problem Summary: I am working on a custom module named Virtual Munim. In my local Frappe setup, the module is correctly placed inside the virtual_munim app, as expected. However, when I deploy the same code to the Frappe Cloud, I noticed that the Virtual Munim module is showing up inside the Frappe app instead of inside the virtual_munim app.
Details:
- Locally, the module structure is correct: the Virtual Munim module resides within the virtual_munim app folder.
- On Frappe Cloud (hosted site), the module is appearing inside the Frappe app (under the ‘Frappe’ directory) instead of inside its own virtual_munim app.
- Both environments use the same codebase, and I have followed the proper deployment process.
- I’ve checked
hooks.pyand themodules.txtfile, and everything seems fine.
My Questions:
- What could be causing this issue where the module is incorrectly linked to the Frappe app on the cloud deployment?
- Are there any additional steps required for Frappe Cloud deployment to ensure the custom module appears under the correct app?
- Is this a known issue with Frappe Cloud deployments, or could it be related to some configuration or environment setting I’m missing?
I would appreciate any insights or suggestions from those who have encountered similar issues or have experience with custom module deployment on Frappe Cloud.
Thank you in advance!
