Having something like in the old docs would be good. Just to make sure I'm not missing anything: I've checked these two pages:
1. https://cloud.google.com/appengine/docs/managed-vms/ 2. https://cloud.google.com/docs/ (The Node.js/Ruby/Python/Go starter) Here is all I could currently find about extending/custorm runtimes: 1. https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes/ 2. https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes/build Basically it says it can be done and describes port 8080, start/stop, healthchecks, logging. But there are no examples at all. And because of the "better" dockerless getting started experience, the user hasn't even seen or worked with any dockerfile yet. Probably not even virtualbox/docker/boot2docker installed. At latest now, this should happen. While it isn't strictly necessary, I wouldn't expect anyone to write a flawless dockerfile without testing it locally. Compared to the old docs, there were examples for extending a standard runtime: 1. https://web.archive.org/web/20150320121928/https://cloud.google.com/appengine/docs/managed-vms/tutorial/step4 (apt-get) 2. https://web.archive.org/web/20150320094050/https://cloud.google.com/appengine/docs/managed-vms/tutorial/step5 (python dependcy) 3. https://web.archive.org/web/20150320175551/https://cloud.google.com/appengine/docs/managed-vms/tutorial/step6 (native c extension) for building a custom runtime 1. https://web.archive.org/web/20150321081655/https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes on top of that, the user had worked with docker through out the basic tutorial already. If this sounds like a rant, then it's because I've mentioned that here already: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/google-appengine-go/Managed$20VM$20GOPATH$20issues/google-appengine-go/LQMhpx447hI/2qgNgNoyl2EJ ,but was told "Getting Started with Managed VMs" experience was painful due to the need > for VirtualBox, boot2docker, and Docker. > I understand that "Getting Started" should be kept as simple as possible and advanced usages kept for later. But it was simply removed. On Friday, March 11, 2016 at 3:10:13 AM UTC+8, Jon Parrott wrote: > > We'd love to hear feedback on how we can make the extending runtime and > building custom runtime pages better as well. > > On Thursday, March 10, 2016 at 1:15:59 AM UTC-8, Su-Au Hwang wrote: >> >> Thanks for the link! >> I've seen Appstart before and it looks like a great solution, albeit not >> officially supported. >> >> I'm just disappointed that they almost gave us a nice solution and then >> removed it again. Although the Image Service and Cloud Storage has never >> been implemented anyways, not even on classic. >> For now I'll write clean code and abstract away the datastore/taskqueue >> other google services completely and replace it with a different >> implementation for testing locally. More work, but the result would be more >> portable and nicer code. >> >> Any hints for making working with MVMs simpler/easier are welcome. >> >> >> On Thursday, March 10, 2016 at 4:06:19 PM UTC+8, pdknsk wrote: >>> >>> I agree with you on most points, but want to point out that this has >>> already been discussed quite a bit with the Google Cloud SDK developers. >>> >>> To read up on (and join) the discussion I recommend to read comment #27 >>> in the following bug report, and the forum discussion mentioned a few >>> comments later. >>> >>> https://code.google.com/p/google-cloud-sdk/issues/detail?id=163#c27 >>> >> -- 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/f9ecc696-20d0-4bad-855b-7c4bf692d388%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
