The documentation now defines modules as the way to structure a big project made of small parts. We have something similar structured the following way:
app.yaml - url: /profile/* script: profile.app - url: /account/* script: account.app - url: /css mime_type: text/css static_dir: css ... account.py (has its own Webapp2 app instance) profile.py (has its own webapp2 app instance) ... css/ js/ Each part (account, profile, etc...) has its own webapp2 instance. I would like to get some comments/feedback on how I structured the project so far. There may be drawbacks that I haven't considered. Also, we are going to split the project in two. The two "sub-projects" need the same database layer. They will also reuse parts I assigned different webapp2 instances to. The only difference is that they will have their own endpoints and own static assets. The end goal is to have two separate custom domains. I don't know if I went the wrong path and should be using modules instead with the current code. Has anyone done anything similar or run into similar issue? Would like to know if we should switch to modules. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7f01290c-7677-4b58-afbe-f22468f78bf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
