blocks|key|4877460|text|我已经创建了一个名为"Fbone“的Flask样板项目，请随时查看并派生:)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4877461|Fbone+(Flask+bone)是一个Flask+(Python微框架)模板/引导/样板应用程序。|4877462|概述|4877463|使用blueprint.|4877464|Integrate和最热门的前端框架:著名的SQLalchemy.|unordered-list-item|4877465|
|4877466|Implement+tricky+"remember+me“by+flask-login.|4877467|4877468|Handle+web+forms+by+flask-wtform.|4877469|4877470|Unit+testing+with+flask-testing和nose为大型项目设计了良好的|4877471|。通过fabric和mod_wsgi轻松部署|4877472|+(example+flask+by+flask-mod_wsgi|4877473|4877474|4877475|顺便说一句，我刚刚发现这个关于用Flask构建一个大型项目的wiki很有用，请检查一下！|4877476|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/imwilsonxu/fbone|1|https://github.com/mitsuhiko/flask/wiki/Large-app-how-to^0|B|5|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|U|4|1|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1J|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1K|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|1L|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1M|8|@]|9|@]|C|$]]|$1|O|3|P|5|L|7|1N|8|@]|9|@]|C|$]]|$1|Q|3|N|5|6|7|1O|8|@]|9|@]|C|$]]|$1|R|3|S|5|L|7|1P|8|@]|9|@]|C|$]]|$1|T|3|N|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|U|3|V|5|L|7|1R|8|@]|9|@]|C|$]]|$1|W|3|X|5|L|7|1S|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|L|7|1T|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]|$1|11|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|1W|8|@]|9|@$A|1X|B|1Y|1|1Z]]|C|$]]|$1|14|3|-4|5|6|7|20|8|@]|9|@]|C|$]]]|15|$16|$5|17|18|19|C|$1A|1B]]|1C|$5|17|18|19|C|$1A|1D]]]]

I have created a Flask boilerplate project called "<a href="https://github.com/imwilsonxu/fbone" rel="noreferrer">Fbone</a>", please feel free to check it out and fork :)

Fbone (Flask bone) is a Flask (Python microframework) template/bootstrap/boilerplate application.

Overview

<ul>
<li>Well designed for big project using blueprint.</li>
<li>Integrate with hottest frontend framework: jQuery / html5boilerplate / bootstrap.</li>
<li>Backed by the famous SQLalchemy.</li>
<li>Implement tricky "remember me" by flask-login.</li>
<li>Handle web forms by flask-wtform.</li>
<li>Unit testing with flask-testing and nose.</li>
<li>Easily deploy via fabric and mod_wsgi (example included).</li>
<li>i18n by flask-babel</li>
</ul>

btw, I just found this <a href="https://github.com/mitsuhiko/flask/wiki/Large-app-how-to" rel="noreferrer">wiki</a> on building a large project with Flask useful, pls check it!

blocks|key|4877371|text|Flask+0.7实现了Blueprints。它们非常适合在不导入主应用程序对象的情况下使用route装饰器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4877372|entityMap|0|LINK|mutability|MUTABLE|url|http://flask.pocoo.org/docs/blueprints/^0|1A|5|C|A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Flask 0.7 implements <a href="http://flask.pocoo.org/docs/blueprints/" rel="noreferrer">Blueprints</a>. They are great for using the <code>route</code> decorator without importing the main application object.

blocks|key|651817|text|请务必阅读+Matt+Wright关于这个主题的+。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|651818|这篇文章的特点是：|651819|MVC+projects|651820|An+example+application+on+Github|unordered-list-item|651821|
|651822|A描述大型烧瓶的结构描述在涉及大型web应用程序时，一般最佳设计实践的描述，如|651823|模式、应用程序工厂、服务和数据迁移等(最有趣的功能)。|ordered-list-item|651824|651825|651826|entityMap|0|LINK|mutability|MUTABLE|url|http://mattupstate.com/blog/how-i-structure-my-flask-applications/|1|https://github.com/mattupstate/overholt^0|0|5|O|1|0|0|0|0|0|W|1|0|0|0|13|0|0|R|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|F|3|G|5|6|7|1B|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|M|3|N|5|6|7|1H|8|@]|D|@]|E|$]]|$1|O|3|P|5|L|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]|13|$5|Y|Z|10|E|$11|14]]]]

Make sure to read Matt Wright's <a href="http://mattupstate.com/blog/how-i-structure-my-flask-applications/" rel="nofollow">wonderful post</a> on the subject.

The post features:

<ol>
<li>A description of a structure for large flask projects</li>
<li><a href="https://github.com/mattupstate/overholt" rel="nofollow">An example application on Github</a></li>
<li>A description of best design practices in general when it comes to large web apps, like the MVC pattern, App factories, Services and Data Migration to name a few (most interesting feature IMHO).</li>
</ol>

blocks|key|1667254|text|我正在做一个(按照我的标准)大型的Flask项目(5000行Python代码，它只完成了一半)。客户希望项目是模块化的，所以我采用了下面的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1667255|我的文件夹结构如下所示：|1667256|├──+__init__.py
├──+modules.yml
├──+config
├──+controllers
│+++└──+...
├──+lib:+Common+functions+I+use+often
│+++└──+...
├──+models
│+++└──+...
├──+static:+All+static+files
│+++├──+css
│+++├──+img
│+++└──+js
└──+templates:+Jinja2+templates
++++└──+...|code-block|syntax|javascript|1667257|在modules.yml中，我定义了模块，包括名称和URL。这样，客户可以在不接触任何Python文件的情况下启用/禁用模块。此外，我还根据模块列表生成菜单。按照惯例，每个模块在controllers/中都有自己的Python-+model，它将从models/加载自己的模块。每个控制器定义一个存储为控制器名称的Blueprint。例如，对于user模块，我在controllers/user.py中有|offset|length|style|CODE|1667258|#+Module+name+is+'user',+thus+save+Blueprint+as+'user'+variable
user+=+Blueprint('user',+__name__)

@user.route('/user/')
def+index():
++++pass|1667259|这样，我就可以读取__init__.py中的modules.yml，并动态加载和注册所有启用的模块：|1667260|#+Import+modules
for+module+in+modules:

++++#+Get+module+name+from+'url'+setting,+exculde+leading+slash
++++modname+=+module['url'][1:]

++++try:
++++++++#+from+project.controllers.<modname>+import+<modname>
++++++++mod+=+__import__(
++++++++++++'project.controllers.'+%2B+modname,+None,+None,+modname
++++++++)
++++except+Exception+as+e:
++++++++#+Log+exceptions+here
++++++++#+[...]

++++mod+=+getattr(mod,+modname)++#+Get+blueprint+from+module
++++app.register_blueprint(mod,+url_prefix=module['url'])|1667261|我希望，这能给你一些启发:)|1667262|entityMap^0|0|0|0|1|B|2H|C|37|5|3G|7|4D|9|4S|4|51|J|0|0|9|B|M|B|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@$K|12|L|13|M|N]|$K|14|L|15|M|N]|$K|16|L|17|M|N]|$K|18|L|19|M|N]|$K|1A|L|1B|M|N]|$K|1C|L|1D|M|N]|$K|1E|L|1F|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|1G|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|1H|8|@$K|1I|L|1J|M|N]|$K|1K|L|1L|M|N]]|9|@]|A|$]]|$1|S|3|T|5|F|7|1M|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1N|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|X|$]]

I'm working on a (by my standards) big Flask project (5000 lines of Python code and it's only half-finished). The customer wants the project to be modular, so I took this apporach:

My folder structure looks like this:

<pre class="lang-none prettyprint-override"><code>├── __init__.py
├── modules.yml
├── config
├── controllers
│ └── ...
├── lib: Common functions I use often
│ └── ...
├── models
│ └── ...
├── static: All static files
│ ├── css
│ ├── img
│ └── js
└── templates: Jinja2 templates
 └── ...
</code></pre>

In <code>modules.yml</code> I define my modules including name and URL. This way the customer is able to enable/disable modules without touching a single Python file. In addition, I generate the menus based on the modules list. By convention every module has it its own Python-module in <code>controllers/</code> that will load its <code>model</code> from <code>models/</code>. Every controller defines a <code>Blueprint</code> stored as the controller's name. E.g. for a <code>user</code> module, I have in <code>controllers/user.py</code>:

<pre class="lang-py prettyprint-override"><code># Module name is 'user', thus save Blueprint as 'user' variable
user = Blueprint('user', __name__)

@user.route('/user/')
def index():
 pass
</code></pre>

This way, I can read the <code>modules.yml</code> in my <code>__init__.py</code> and load and register all enabled modules dynamically:

<pre class="lang-py prettyprint-override"><code># Import modules
for module in modules:

 # Get module name from 'url' setting, exculde leading slash
 modname = module['url'][1:]

 try:
 # from project.controllers.&lt;modname&gt; import &lt;modname&gt;
 mod = __import__(
 'project.controllers.' + modname, None, None, modname
 )
 except Exception as e:
 # Log exceptions here
 # [...]

 mod = getattr(mod, modname) # Get blueprint from module
 app.register_blueprint(mod, url_prefix=module['url'])
</code></pre>

I hope, this can be some inspiration for you :)

blocks|key|651864|text|我在一个建立在Flask之上的社交网络上工作。我的项目的特别之处在于，服务器纯粹是为API端点提供服务，而前端是一个单页面的主干应用程序。我采用的Flask结构如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|651865|+`├──+app+++++│+++├──+api`|code-block|syntax|javascript|651866|+`│+++│+++├──+auth.py+++++│+++│+++└──+...+++++│+++├──+app.py+++++│+++├──+common+++++│+++│+++├──+constants.py+++++│+++│+++├──+helpers.py+++++│+++│+++├──+response.py+++++│+++│+++└──+...+++++│+++├──+config.py+++++│+++├──+extensions.py+++++│+++├──+frontend+++++│+++│+++└──+controllers.py+++++│+++├──+static+++++│+++│+++└──+...+++++│+++├──+templates+++++│+++│+++├──+app.html+++++│+++│+++└──+...+++++│+++└──+users+++++│+++++++├──+UserConstants.py+++++│+++++++├──+UserForms.py+++++│+++++++├──+UserHelpers.py+++++│+++++++├──+UserModels.py+++++│+++++++└──+__init__.py+++++├──+alembic+++++%7C+++├──+version+++++│+++└──+...+++++├──+tests+++++│+++└──+...`+|651867|你可以阅读我在主题here上写的更深入的帖子。我发现将不同的功能区域划分到自己的文件夹中要直观得多。|offset|length|651868|我前段时间编写了代码，并且完全开源了！你可以在on+github上查看。|651869|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.sampingchuang.com/structure-a-large-flask-api-backend-app/|1|https://github.com/spchuang/DoubleDibz-tutorial/tree/master/FINAL^0|0|0|0|9|4|0|0|N|9|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|I|3|J|5|6|7|11|8|@]|9|@$K|12|L|13|1|14]]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$K|16|L|17|1|18]]|A|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]]]

I worked on a social network built on top of Flask. The special thing about my project was that the server is purely serving API endpoints and the frontend is a one-page Backbone app. The Flask structure I took is the following:

<code>
 ├── app
 │ ├── api 
 │ │ ├── auth.py
 │ │ └── ...
 │ ├── app.py
 │ ├── common
 │ │ ├── constants.py
 │ │ ├── helpers.py
 │ │ ├── response.py
 │ │ └── ...
 │ ├── config.py
 │ ├── extensions.py
 │ ├── frontend
 │ │ └── controllers.py
 │ ├── static
 │ │ └── ...
 │ ├── templates
 │ │ ├── app.html
 │ │ └── ...
 │ └── users
 │ ├── UserConstants.py
 │ ├── UserForms.py
 │ ├── UserHelpers.py
 │ ├── UserModels.py
 │ └── __init__.py
 ├── alembic
 | ├── version
 │ └── ...
 ├── tests
 │ └── ...
</code>

You can read the more in-depth post I wrote on the topic <a href="http://blog.sampingchuang.com/structure-a-large-flask-api-backend-app/" rel="noreferrer">here</a>. I found it to be much more intuitive to separate different functional areas to its own folder. 

I worked on the code a while ago and open sourced it completely! You can check it out <a href="https://github.com/spchuang/DoubleDibz-tutorial/tree/master/FINAL" rel="noreferrer">on github</a>.

blocks|key|652059|text|我从头开始创建了一个Flask应用程序yapper，并将其与gulp集成在一起进行前端和后端开发。它是一个简单的博客引擎，但可以很容易地进行修改，以便根据需要进行开发。它使用蓝图进行了很好的结构。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|652060|签出项目页面yapper|652061|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/brijeshb42/yapper^0|J|6|0|6|6|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

I have created a Flask app yapper from scratch and integrated it with gulp for both frontend and backend development.
It is a simple blog engine but can be easily modified for developing according to requirements. It is well structured using Blueprints.

Checkout the project page <a href="https://github.com/brijeshb42/yapper" rel="nofollow" title="yapper">yapper</a>

I'm building my first Flask app and I can't figure out a good, clean Pythonic way of organizing my application.
I don't want to have everything in a single .py file as in their example.
I would like to have each part of my app in a separate module.
What would be a good way to organize things?

How to organize a relatively large Flask application?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在构建我的第一个Flask应用程序，但我找不到一个好的、干净的Pythonic方式来组织我的应用程序。我不想把所有东西都放在一个.py文件中，就像他们的例子一样。我希望我的应用程序的每个部分都在一个单独的模块中。什么是组织事物的好方法？

问如何组织一个相对较大的Flask应用程序？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何组织一个相对较大的Flask应用程序？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何组织一个相对较大的Flask应用程序？
EN