Question consultation regarding the creation process of the Dash Cloud project

Plotly Cloud
1

I started to try using Dash Cloud to publish applications. Currently, its basic functions are very convenient and fast. For sample applications with a relatively simple structure (for example: https://dash-cloud-deploy-demo20250823.plotly.app), the whole process is very convenient.

However, when I tried to test some Dash applications with a more complex project structure (for example: GitHub - CNFeffery/feffery-antd-docs: feffery-antd-components在线文档源码), in order to avoid the circular import problem caused by directly importing the Dash application instance from app.py in other modules, some users are accustomed to defining the Dash application instance in a separate server.py. This causes the following two checks to fail during the project upload stage:

image
image1041×366 20.1 KB

Should we consider adding an additional configuration parameter input box in the project upload interface, allowing users to manually specify the py file corresponding to the Dash instantiation?

2

Thank you for your feedback @CNFeffery . We recently discussed this option and have added it to our backlog to address.

1 Like
3

Absolutely, this is top of mind for us. We’re planning to build a more generic run command system so that apps with different entry point file names will run without issue. You can follow along with this feature here by commenting here: https://portal.productboard.com/ppdpxatzzfgdshaelymecwxn/tabs/10-under-consideration

We’re considering this as “automate pre-flight checks” as we would detect the right file to use as the entry point for your app.