blocks|key|281323|text|我首先来看一下模块，至少有以下几个原因：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|281324|模块实际上在许多方面(几乎)相当于整个(单模块)应用程序在旧的文档/引用中，因此一旦模块在应用程序层次结构中的位置得到澄清，引用应用程序上下文的各种帖子通常可以推断为仅限于模块的上下文。|unordered-list-item|281325|现在，一个应用程序可以对不同的模块使用不同的语言/沙箱(参见在google应用程序引擎项目上运行Java和PHP)，甚至可以使用同一模块的不同版本(参见的部分升级)。|offset|length|281326|就我个人而言，我会坚持使用建议多模块应用程序结构--每个模块都有自己的目录，在应用程序目录下的一个级别：|281327|​|281328|📷|atomic|281329|281330|该应用程序的顶部将包含每个应用程序的倾诉(不适用于特定模块)：dispatch.yaml、cron.yaml、index.yaml和queue.yaml。注意，cron作业和任务队列定义属于这里(但是没有什么阻止您根据请求的路径将各种cron作业路由/分配到各个模块)。|style|CODE|281331|我也会放置在应用程序的顶级dir任何文件/目录，我想要在多个模块之间共享的干燥方式。这些文件/dirs将由模块共享，方法是将它们在各自的模块内进行符号链接，以便模块在部署时获得自己的副本。几乎所有可以作为单独文件或目录存在的都可以通过以下方式共享：|BOLD|281332|模板、图像、脚本、CSS、宏、数据存储模型定义、python模块--无论您需要什么|281333|第三方库，例如如何从中的一个模块访问一个独立的库？|281334|甚至模块的.yaml配置的一部分！例如：跨多个YAML文件？|281335|最后，推荐的特定模块的文件/dir结构可能进一步取决于模块语言/沙箱、使用的框架、开发人员的风格/首选项等。我认为不可能提供一种适合于所有情况的、有效/可接受的建议。|281336|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/33319824/run-both-java-and-php-on-google-app-engine-project/33320938#33320938|1|https://stackoverflow.com/questions/33993600/google-app-engine-upgrading-part-by-part/34001871#34001871|2|https://cloud.google.com/appengine/docs/python/modules/#Python_Configuration|3|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/e3321320160837724158e129e9ce4fc0.png|imageAlt|4|https://stackoverflow.com/questions/34973058/how-do-i-access-a-vendored-library-from-a-module-in-python-google-app-engine/34985211#34985211|5|https://stackoverflow.com/questions/33307128/do-i-need-to-copy-skip-files-across-multiple-yaml-files/33308640#33308640^0|0|0|U|Q|0|24|5|1|0|D|2|2|0|0|0|1|3|0|0|V|D|19|9|1J|A|1U|A|0|34|C|0|0|15|0|0|P|7|I|4|0|0|U|5|5|K|A|5|0|0|2B|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1S|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1T|8|@]|9|@$G|1U|H|1V|1|1W]|$G|1X|H|1Y|1|1Z]]|A|$]]|$1|I|3|J|5|6|7|20|8|@]|9|@$G|21|H|22|1|23]]|A|$]]|$1|K|3|L|5|6|7|24|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|25|8|@]|9|@$G|26|H|27|1|28]]|A|$]]|$1|P|3|L|5|6|7|29|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2A|8|@$G|2B|H|2C|S|T]|$G|2D|H|2E|S|T]|$G|2F|H|2G|S|T]|$G|2H|H|2I|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|2J|8|@$G|2K|H|2L|S|W]]|9|@]|A|$]]|$1|X|3|Y|5|D|7|2M|8|@$G|2N|H|2O|S|W]]|9|@]|A|$]]|$1|Z|3|10|5|D|7|2P|8|@$G|2Q|H|2R|S|W]]|9|@$G|2S|H|2T|1|2U]]|A|$]]|$1|11|3|12|5|D|7|2V|8|@$G|2W|H|2X|S|W]|$G|2Y|H|2Z|S|T]]|9|@$G|30|H|31|1|32]]|A|$]]|$1|13|3|14|5|6|7|33|8|@$G|34|H|35|S|W]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|36|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]|1D|$5|18|19|1A|A|$1B|1E]]|1F|$5|18|19|1A|A|$1B|1G]]|1H|$5|1I|19|1J|A|$1K|1L|1M|-4]]|1N|$5|18|19|1A|A|$1B|1O]]|1P|$5|18|19|1A|A|$1B|1Q]]]]

I'd first take a look at modules, at least for these reasons: 

<ul>
<li>modules really are in many respects (almost) equivalents to entire (single-module) apps in older docs/references, so once a module's position in the app's hierarchy is clarified various posts referencing an app-context can usually be extrapolated to just a module-only context.</li>
<li>nowadays an app can use different languages/sandboxes for different modules (see <a href="https://stackoverflow.com/questions/33319824/run-both-java-and-php-on-google-app-engine-project/33320938#33320938">Run both Java and PHP on google app engine project</a>) or even for different versions of the same module (see <a href="https://stackoverflow.com/questions/33993600/google-app-engine-upgrading-part-by-part/34001871#34001871">Google App Engine upgrading part by part</a>)</li>
</ul>

Personally I'd stick with <a href="https://cloud.google.com/appengine/docs/python/modules/#Python_Configuration" rel="nofollow noreferrer">the recommended</a> multi-module app structure - each module having its own directory, one level below the app's directory:

<a href="https://i.stack.imgur.com/Y5gcq.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Y5gcq.png" alt="enter image description here"></a>

The app's top dir would hold the per-app configs (which aren't applicable to a particular module): <code>dispatch.yaml</code>, <code>cron.yaml</code>, <code>index.yaml</code>, and <code>queue.yaml</code>. Note that the cron jobs and task queues definitions belong here (but nothing stops you from routing/dispatching various cron jobs to various modules based on the requested paths).

I'd also place in the app's top level dir any files/directories I'd like to share across multiple modules in the DRY way. These files/dirs would be shared by a module by symlinking them inside the respective modules so that the module gets its own copy at deployment. Almost anything that can exist as a separate file or directory can be shared this way:

<ul>
<li>templates, images, scripts, CSS, macros, datastore models definitions, python modules - whatever you need</li>
<li>3rd party libs, for example <a href="https://stackoverflow.com/questions/34973058/how-do-i-access-a-vendored-library-from-a-module-in-python-google-app-engine/34985211#34985211">How do I access a vendored library from a module in Python Google App Engine?</a></li>
<li>even portions of the module's <code>.yaml</code> configuration! for example: <a href="https://stackoverflow.com/questions/33307128/do-i-need-to-copy-skip-files-across-multiple-yaml-files/33308640#33308640">Do I need to copy `skip_files` across multiple YAML files?</a></li>
</ul>

Finally the recommended files/dir structure of a particular module may further depend on the module language/sandbox, the framework(s) used, the developer's style/preferences, etc. I don't think it's possible to provide a one-size-fits-all recommendation which would be effective/acceptable in all cases.

blocks|key|510150|text|端点只是基本REST+url的RPC+(强类型)版本，它的另一个优点是可以用于生成客户端库。因此端点配置和定义与模块(即移动后端)与REST对应的目录相同。换句话说，如果您在Module1中有一个REST端点用于“用户登录”，那么您应该将“用户登录”端点放在module1目录中。此外，如果您不喜欢符号链接方法，可以将module1.yaml文件移到一个级别上，然后整个模块可以从“公共”目录导入。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|510151|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Endpoints are just RPC (strongly typed) versions of basic REST url's with the added advantage that they can be used to Generated client side libraries. So the endpoint config and definitions belong in the SAME directory as the module (ie mobile-backend) as their REST counterpart would. In other words, if you have (or would have) a REST endpoint in Module1 for "user login", then you should put the "user login" Endpoint in the module1 directory. Further, if you don't like the symlink approach, you can move your module1.yaml file UP one level and then that whole module can import from a "common" directory.

I see that there is already an <a href="https://stackoverflow.com/questions/48458/project-structure-for-google-app-engine">answer</a> to this question but I feel its outdated. Many things have changes since then. There are now <a href="https://cloud.google.com/appengine/docs/python/modules/" rel="nofollow noreferrer">modules</a>, <a href="https://cloud.google.com/appengine/docs/python/endpoints/" rel="nofollow noreferrer">cloud_endpoints</a> and <a href="https://cloud.google.com/appengine/docs/python/tools/webapp/" rel="nofollow noreferrer">webapp2</a>. What should be the good directory structure for my project which allows me to add/modify features easily.

For example I should be able to manage:

<ol>
<li>Modules.</li>
<li>Cron jobs.</li>
<li>Task queues.</li>
<li>Cloud endpoints.</li>
</ol>

New project structure for Google App Engine

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我看到这个问题已经有了一个，但我觉得它已经过时了。从那以后，许多事情都发生了变化。现在有，和。什么应该是我的项目的良好目录结构，它允许我轻松地添加/修改特性。例如，我应该能够管理：模块。克伦·乔布斯。任务队列。云端点。

问的新项目结构
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问的新项目结构EN