azure web应用部署
The story starts with implementing a light-weighted dashboard app for some end users from the business side. Looking into the market nowadays, there is a wide range of data visualization tools e.g. Streamlit, Dash, Panel. We choose Dash because of prior familiarity to plotly as well as a relatively larger user foundation. Here comes the story.
吨他的故事开始与实施光加权信息中心应用从业务方面的一些终端用户。 展望当今市场,有各种各样的数据可视化工具,例如Streamlit,Dash,Panel。 我们之所以选择Dash是因为需要事先熟悉,并且需要相对较大的用户基础。 故事来了。
We will skip the talk of Dash app layout as there are already many different opinions about the best practices in the user forum. We generally split the app into four main modules, app.py where we instantiate the app object, components.py which holds different parts of the features, callbacks.py with all the callbacks in relation to components, and utils.py with auxiliary backend functions.
我们将跳过Dash应用程序布局的讨论,因为在用户论坛中已经有许多关于最佳实践的意见。 通常,我们将应用分为四个主要模块:app.py(用于实例化应用对象),components.py(用于保存功能的不同部分),callbacks.py(具有与组件相关的所有回调)和utils.py(具有辅助后端)功能。
![Image for post](https://i-blog.csdnimg.cn/blog_migrate/532171dbe1c34ca86287b92c9141a710.png)