Thanks. I did eventually find that. Google cloud is getting to be a lot like Microsoft. Everything is documented, but there are so many docs it’s impossible to find what you are looking for.
> On Feb 24, 2017, at 4:20 PM, 'Adam (Cloud Platform Support)' via Google App > Engine <google-appengine@googlegroups.com> wrote: > > In your case to deploy the 'reporting' service you would use: > > appcfg.py update reporting.yaml > > You can list any number of .yaml files for services to deploy after > 'appcfg.py update'. The usage is given in the documentation under Deploying > multiple service applications > <https://cloud.google.com/appengine/docs/standard/python/tools/uploadinganapp#to_deploy_multiple_services>. > > On Friday, February 24, 2017 at 10:46:40 AM UTC-5, Joshua Smith wrote: > I have a process I need to let run longer than 10 minutes, and I have been > using “backends” for this. > > I saw the deprecation warning, so I decided to try making it into a module > instead. The documentation on this is a complete mess. Hey google: You need > to go clean this up. There are a whole lot of different pages that describe > bits and pieces of the puzzle, but I can’t find anything that tells me what I > actually need to do. It doesn’t help that backends became modules became > services. SMDH. > > Anyway, I found the article that told me how to generate a .yaml for my > module based on my old backends.yaml and my app.yaml. My module is called > “reporting” so I have reporting.yaml. > > After making that and deleting my backends.yaml, I clicked deploy on the GAE > launcher, but that didn’t do anything about my module. > > So I guess I need to run appcfg.py manually? But I have no idea what > arguments to give it. > > I just want to push the latest code up, and then I will hit the module with a > URL. > > I used to do this with: appcfg.py backends <dir> update > > What command should I issue to get the same result with my “reporting” module? > > -Joshua > > > -- > 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 google-appengine+unsubscr...@googlegroups.com > <mailto:google-appengine+unsubscr...@googlegroups.com>. > To post to this group, send email to google-appengine@googlegroups.com > <mailto:google-appengine@googlegroups.com>. > Visit this group at https://groups.google.com/group/google-appengine > <https://groups.google.com/group/google-appengine>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/697eccc5-b17a-4852-8b09-12627d347d10%40googlegroups.com > > <https://groups.google.com/d/msgid/google-appengine/697eccc5-b17a-4852-8b09-12627d347d10%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. 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/4872BB30-48FF-4245-8599-20FD67874BB0%40gmail.com. For more options, visit https://groups.google.com/d/optout.
