Re: [google-appengine] New App Engine Managed VM Docs

['Alex Martelli' via Google App Engine]

Just a personal input/data point -- writing not as a Googler but as a
"Python guru":-)

Currently writing the 3rd edition of Python in a Nutshell (in my copious
personal time), I've recently finished the "serving HTTP" chapter (the book
is already available in Early Release form at the O'Reilly website, check
it out:-). For the purpose, I thoroughly tested lightweight frameworks
(rich frameworks such as django, web2py, and the like, though I mentioned
them, aren't really "my thang"). Specifically: falcon, flask, bottle, and
webapp2.

Of the four, webapp2 remains my favorite (admittedly I started out knowing
it much better than the others, which may have biased me). Next in order of
preference, falcon, bottle, flask -- all good, but the most popular, flask,
is accruing so much extras that it barely qualifies as "lightweight" any
more.

If webapp2 becomes easy to offer patches for again, I'll spend personal
time (once the Nutshell is finished -- give me a few more months!-) helping
there -- indeed I'll volunteer to vet pull requests if gurus to vet them
are needed -- to help keep out the kinds of deep integration with unrelated
components (such as the admittedly superb templating framework jinjia2)
which are fattening up flask:-(.

I sure hope (very personal preference) that webapp2 isn't put out to
pasture... should it be, I might either fork it, or give up and move to
falcon for new projects (and maybe volunteer to help out on THAT framework).

Again, just personal preferences -- but, ones based on almost 20 years'
experience with Python (starting with a personal website project using CGI)
and on being a Fellow of the PSF and a winner of the Frank Willison
Memorial Award for contributions to Python:-).


Alex


On Mon, Feb 22, 2016 at 2:34 PM, Karl MacMillan 
wrote:

>
> On Feb 22, 2016, at 4:40 PM, 'Jon Parrott' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
> > if you ask me, you really should just put webapp2 into maintenance only
> mode and suggest people move on. There are no advantages over more popular
> frameworks and plenty of downsides.
>
> In general we want to align with the Python community. Whether we update
> our docs to point to Flask over webapp2 is currently a point of discussion
> - but I'm personally for it.
>
>
> If you don’t make the change (or maybe until), can I strongly suggest you
> include some discussion that makes it clear the level of support for
> webapp2. Like I said - I went with that option on the mistaken impression
> that it was well supported by Google. That’s the _only_ thing that
> irritates me about this whole situation. I believe the docs lead me down a
> path without warning me of the true consequences. Even a basic “webapp2 is
> community supported framework” description would make it clearer.
>
> No matter what we do there, there should be some way for people who are
> currently using webapp2 currently to provide patches.
>
>
> I’d certainly appreciate that. Despite my complaints, I’m not itching to
> port all of my code off of webapp2 because it’s working fine.
>
> Karl
>
> Putting webapp2 in maintenance only mode is not currently our decision as
> we do not own the package (it's a third-party package). If we do gain
> ownership of it, we will likely put it into a community-supported model.
>
> On Mon, Feb 22, 2016 at 1:32 PM Karl MacMillan 
> wrote:
>
>> On Feb 22, 2016, at 4:14 PM, 'Jon Parrott' via Google App Engine <
>> google-appengine@googlegroups.com> wrote:
>>
>> > Is that new? Last I looked I believe NDB was not supported. If I could
>> suggest it would be helpful to use more specific terminology than Datastore
>> on that page.
>>
>> It's not new as far as I know - ndb and db have traditionally be the way
>> to access datastore in App Engine, so it's somewhat implied. I'll see if I
>> can't make the docs a bit more clear there.
>>
>>
>> Hmm - maybe I was wanting ndb in a non-compat python runtime. It’s been a
>> while.
>>
>> > So - I’ll call your bluff. Tell me how to submit a patch for the issue
>> I pointed to and I’ll happily do so.
>>
>> You make some excellent points. I will move webapp2 to github, take
>> ownership of it, and I'll be happy to review and merge your patch as well
>> as publish a new version of webapp2 to PyPI. This process takes some time,
>> so I will update this list once that is done.
>>
>>
>> Hah - fair enough. I’ll send you that patch when you’re ready.
>>
>> BUT - if you ask me, you really should just put webapp2 into maintenance
>> only mode and suggest people move on. There are no advantages over more
>> popular frameworks and plenty of downsides.
>>
>> One note - last I looked much of the session handling code was completely
>> broken (
>> https://webapp-improved.appspot.com/api/webapp2_extras/sessions.html). I
>> ended up just rolling my own after my initial bug report was ignored.
>>
>> Karl
>>
>>
>> On Mon, Feb 22, 2016 at 1:01 PM Karl MacMillan 

[google-appengine] Re: Asynchronous Deployment With Java AppEngine SDK

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Andrew,

You'll need to wait until the previous deployment completes. In most 
scripting languages, it would be a matter of explicitly making your calls 
*asynchronous* in order to even run into this 409 error. Are you perhaps 
using NodeJS, which is a somewhat asynchronous language often used for 
scripting?

Best wishes,

Nick


On Monday, February 22, 2016 at 11:31:09 AM UTC-5, Andrew Teall wrote:
>
> Hi,
> We're trying to deploy multiple modules and managed VMs using the Java 
> AppEngine SDK. We are currently using a script with a  for loop that 
> backgrounds each call to the appcfg.sh and waiting 30 seconds between 
> starting each deploy. However we see 409 conflicts pretty often. Is there a 
> better way to accomplish this or does anyone have any experience getting 
> this to work with 100% success.
>
> Thanks,
> Andrew
>

-- 
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/404e9bb9-a432-4c8c-adbf-a2c8a2a2fca3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Elevated Images Service Errors

[David Fischer]

Thanks for the update, John.



On Monday, February 22, 2016 at 2:19:49 PM UTC-8, John Lowry wrote:
>
> Hi,
>
> Google Cloud support here.
>
> Just to confirm that we did have an incident that caused elevated errors 
> for the get_serving_url() API call starting at 12:50 PST today.
>
> We have applied a fix and the error rate has been steadily decreasing 
> since 13:25.
>
> I will post to this thread if we have any significant updates.
>
> John Lowry
>
> On Monday, February 22, 2016 at 1:57:53 PM UTC-8, David Fischer wrote:
>>
>> I'm seeing elevated error levels with the request to "get_serving_url" 
>> and for completely valid images and formats (PNGs and JPGs). It is not 
>> failing 100% but I'm seeing errors at a much higher rate than normal. I've 
>> had about 100 errors in the past hour and it started about an hour ago.
>>
>> Is anyone else seeing the same?
>>
>> While testing this, I uploaded PNGs taken directly as screenshots and 
>> still saw the problem. These images do not cause the same problem on the 
>> dev appserver and I'm unable to reproduce it locally. Interestingly enough, 
>> it took about 3 minutes to post my 51kb image to this post. That might be 
>> unrelated.
>>
>>
>> Traceback (most recent call last):
>>   File "/base/data/home/apps/.../views.py", line x 
>> 
>> xx,
>>  in ajax_upload_image
>> url_thumbnail = images.get_serving_url(files[0].key(), size=150, 
>> secure_url=True)
>>   File 
>>
>> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py"
>> ,
>>  line 1794, in get_serving_url
>> return rpc.get_result()
>>   File 
>>
>> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py"
>> ,
>>  line 613, in get_result
>> return self.__get_result_hook(self)
>>   File 
>>
>> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py"
>> ,
>>  line 1892, in get_serving_url_hook
>> raise _ToImagesError(e, readable_blob_key)
>> TransformationError
>>
>>
>>

-- 
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/4343f7bd-2444-4299-9fdc-86dd4f50503d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New App Engine Managed VM Docs

[Karl MacMillan]

> On Feb 22, 2016, at 4:40 PM, 'Jon Parrott' via Google App Engine 
>  wrote:
> 
> > if you ask me, you really should just put webapp2 into maintenance only 
> > mode and suggest people move on. There are no advantages over more popular 
> > frameworks and plenty of downsides.
> 
> In general we want to align with the Python community. Whether we update our 
> docs to point to Flask over webapp2 is currently a point of discussion - but 
> I'm personally for it.

If you don’t make the change (or maybe until), can I strongly suggest you 
include some discussion that makes it clear the level of support for webapp2. 
Like I said - I went with that option on the mistaken impression that it was 
well supported by Google. That’s the _only_ thing that irritates me about this 
whole situation. I believe the docs lead me down a path without warning me of 
the true consequences. Even a basic “webapp2 is community supported framework” 
description would make it clearer.

> No matter what we do there, there should be some way for people who are 
> currently using webapp2 currently to provide patches.
> 

I’d certainly appreciate that. Despite my complaints, I’m not itching to port 
all of my code off of webapp2 because it’s working fine.

Karl

> Putting webapp2 in maintenance only mode is not currently our decision as we 
> do not own the package (it's a third-party package). If we do gain ownership 
> of it, we will likely put it into a community-supported model.
> 
> On Mon, Feb 22, 2016 at 1:32 PM Karl MacMillan  > wrote:
>> On Feb 22, 2016, at 4:14 PM, 'Jon Parrott' via Google App Engine 
>> > > wrote:
>> 
>> > Is that new? Last I looked I believe NDB was not supported. If I could 
>> > suggest it would be helpful to use more specific terminology than 
>> > Datastore on that page.
>> 
>> It's not new as far as I know - ndb and db have traditionally be the way to 
>> access datastore in App Engine, so it's somewhat implied. I'll see if I 
>> can't make the docs a bit more clear there.
>> 
> 
> Hmm - maybe I was wanting ndb in a non-compat python runtime. It’s been a 
> while.
> 
>> > So - I’ll call your bluff. Tell me how to submit a patch for the issue I 
>> > pointed to and I’ll happily do so.
>> 
>> You make some excellent points. I will move webapp2 to github, take 
>> ownership of it, and I'll be happy to review and merge your patch as well as 
>> publish a new version of webapp2 to PyPI. This process takes some time, so I 
>> will update this list once that is done.
>> 
> 
> Hah - fair enough. I’ll send you that patch when you’re ready.
> 
> BUT - if you ask me, you really should just put webapp2 into maintenance only 
> mode and suggest people move on. There are no advantages over more popular 
> frameworks and plenty of downsides.
> 
> One note - last I looked much of the session handling code was completely 
> broken (https://webapp-improved.appspot.com/api/webapp2_extras/sessions.html 
> ). I 
> ended up just rolling my own after my initial bug report was ignored.
> 
> Karl
> 
> 
>> 
>> On Mon, Feb 22, 2016 at 1:01 PM Karl MacMillan > > wrote:
>>> On Feb 22, 2016, at 3:44 PM, 'Jon Parrott' via Google App Engine 
>>> >> > wrote:
>>> 
>>> Are there plans to port over NDB for datastore access on managed VMs?
>>> 
>>> There is on-going discussion about NDB for Cloud Datastore here 
>>> .
>>>  The tl;dr is that basically it's possible, it's planned, but its 
>>> contingent on the next release of the Cloud Datastore API and decoupling 
>>> NDB from the App Engine SDK.
>>> 
>> 
>> Great.
>> 
>>> That being said, you can absolutely continue use NDB in Managed VMs by 
>>> using runtime: python-compat 
>>> .
>>>  
>>> 
>> 
>> Is that new? Last I looked I believe NDB was not supported. If I could 
>> suggest it would be helpful to use more specific terminology than Datastore 
>> on that page.
>> 
>>> Is webapp2 going to be deprecated
>>> 
>>> There are no present plans that I'm aware of to deprecate webapp2. Because 
>>> webapp2 is a WSGI-compliant web framework and is not itself tied to App 
>>> Engine, you can use it in Standard, Managed VMs, and pretty much anywhere 
>>> else. It'll continue to work everywhere WSGI works.
>> 
>> Sure - I currently use it on GCE as well just to not use two frameworks. But 
>> it is abandoned as far as I can tell - there are bugs that have not been 
>> addressed in years.
>> 
>>> It's also an open-source project and patches are always welcome.
>>> 

[google-appengine] Re: Elevated Images Service Errors

['John Lowry' via Google App Engine]

Hi,

Google Cloud support here.

Just to confirm that we did have an incident that caused elevated errors 
for the get_serving_url() API call starting at 12:50 PST today.

We have applied a fix and the error rate has been steadily decreasing since 
13:25.

I will post to this thread if we have any significant updates.

John Lowry

On Monday, February 22, 2016 at 1:57:53 PM UTC-8, David Fischer wrote:
>
> I'm seeing elevated error levels with the request to "get_serving_url" and 
> for completely valid images and formats (PNGs and JPGs). It is not failing 
> 100% but I'm seeing errors at a much higher rate than normal. I've had 
> about 100 errors in the past hour and it started about an hour ago.
>
> Is anyone else seeing the same?
>
> While testing this, I uploaded PNGs taken directly as screenshots and 
> still saw the problem. These images do not cause the same problem on the 
> dev appserver and I'm unable to reproduce it locally. Interestingly enough, 
> it took about 3 minutes to post my 51kb image to this post. That might be 
> unrelated.
>
>
> Traceback (most recent call last):
>   File "/base/data/home/apps/.../views.py", line x 
> 
> xx,
>  in ajax_upload_image
> url_thumbnail = images.get_serving_url(files[0].key(), size=150, 
> secure_url=True)
>   File 
>
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py"
> ,
>  line 1794, in get_serving_url
> return rpc.get_result()
>   File 
>
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py"
> ,
>  line 613, in get_result
> return self.__get_result_hook(self)
>   File 
>
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py"
> ,
>  line 1892, in get_serving_url_hook
> raise _ToImagesError(e, readable_blob_key)
> TransformationError
>
>
>

-- 
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/5b70e393-f600-424e-b8de-3a1adcaa0636%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Elevated Images Service Errors

[David Fischer]

I'm seeing elevated error levels with the request to "get_serving_url" and 
for completely valid images and formats (PNGs and JPGs). It is not failing 
100% but I'm seeing errors at a much higher rate than normal. I've had 
about 100 errors in the past hour and it started about an hour ago.

Is anyone else seeing the same?

While testing this, I uploaded PNGs taken directly as screenshots and still 
saw the problem. These images do not cause the same problem on the dev 
appserver and I'm unable to reproduce it locally. Interestingly enough, it 
took about 3 minutes to post my 51kb image to this post. That might be 
unrelated.


Traceback (most recent call last):
  File "/base/data/home/apps/.../views.py", line x 

xx,
 in ajax_upload_image
url_thumbnail = images.get_serving_url(files[0].key(), size=150, 
secure_url=True)
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py"
,
 line 1794, in get_serving_url
return rpc.get_result()
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py"
,
 line 613, in get_result
return self.__get_result_hook(self)
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py"
,
 line 1892, in get_serving_url_hook
raise _ToImagesError(e, readable_blob_key)
TransformationError


-- 
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/9dac8e02-ef70-4f2d-b0e0-1fa31c68878e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Domain pointing issue

[Andrei Kamarouski]

All is good - I don't checked availability settings for course (after 
making it public I can see it). :) Thx for help!  

On Tuesday, February 23, 2016 at 12:08:16 AM UTC+3, joshuamo wrote:
>
> If I access http://appid.appspot.com/, it throws me a redirect to 
> /sample/course?use_last_location=true.  The redirect then throws an HTTP 
> 404.  From what I can see myself, this is consistent between appspot.com 
> address and the custom domain address.  The 404 error page also appears to 
> be a custom one?  So it's hitting your app and being processed by app code, 
> at some level.
>
> Potentially, there's an auth layer in your code that's preventing the 
> access for me, and not for you.  Perhaps that's failing on the custom 
> domain, as well.
>
> On Mon, Feb 22, 2016 at 12:51 PM, Andrei Kamarouski  > wrote:
>
>> appspot is ok. custom domain not. i replaced always with optional in 
>> secure handlers records (from support article it does seem relevant choice 
>> too). does it cause errors? 
>>
>> On Monday, February 22, 2016 at 11:45:36 PM UTC+3, joshuamo wrote:
>>>
>>> 404 also occurs if you go to the appspot.com URL for your app, so this 
>>> would be an issue in code or app.yaml configuration.
>>>
>>> On Mon, Feb 22, 2016 at 11:47 AM, Andrei Kamarouski  
>>> wrote:
>>>
 Ok. Seems redirect is gone. But now I get – Unable to access requested 
 page. HTTP status code: 404. 

 -- 
 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-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@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/02f99b3c-25b3-4a64-8be5-e0c70351a55a%40googlegroups.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>>
>>> Josh Moore |  Cloud Solutions Engineer |  josh...@google.com |  
>>>
>> -- 
>> 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-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@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/5ca1dc7f-fada-4b2e-b866-3efec13144f6%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Josh Moore |  Cloud Solutions Engineer |  josh...@google.com 
>  |  
>

-- 
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/09b65ebc-29af-4c08-bee4-2f85c050d4a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New App Engine Managed VM Docs

['Jon Parrott' via Google App Engine]

> if you ask me, you really should just put webapp2 into maintenance only
mode and suggest people move on. There are no advantages over more popular
frameworks and plenty of downsides.

In general we want to align with the Python community. Whether we update
our docs to point to Flask over webapp2 is currently a point of discussion
- but I'm personally for it. No matter what we do there, there should be
some way for people who are currently using webapp2 currently to provide
patches.

Putting webapp2 in maintenance only mode is not currently our decision as
we do not own the package (it's a third-party package). If we do gain
ownership of it, we will likely put it into a community-supported model.

On Mon, Feb 22, 2016 at 1:32 PM Karl MacMillan  wrote:

> On Feb 22, 2016, at 4:14 PM, 'Jon Parrott' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
> > Is that new? Last I looked I believe NDB was not supported. If I could
> suggest it would be helpful to use more specific terminology than Datastore
> on that page.
>
> It's not new as far as I know - ndb and db have traditionally be the way
> to access datastore in App Engine, so it's somewhat implied. I'll see if I
> can't make the docs a bit more clear there.
>
>
> Hmm - maybe I was wanting ndb in a non-compat python runtime. It’s been a
> while.
>
> > So - I’ll call your bluff. Tell me how to submit a patch for the issue
> I pointed to and I’ll happily do so.
>
> You make some excellent points. I will move webapp2 to github, take
> ownership of it, and I'll be happy to review and merge your patch as well
> as publish a new version of webapp2 to PyPI. This process takes some time,
> so I will update this list once that is done.
>
>
> Hah - fair enough. I’ll send you that patch when you’re ready.
>
> BUT - if you ask me, you really should just put webapp2 into maintenance
> only mode and suggest people move on. There are no advantages over more
> popular frameworks and plenty of downsides.
>
> One note - last I looked much of the session handling code was completely
> broken (
> https://webapp-improved.appspot.com/api/webapp2_extras/sessions.html). I
> ended up just rolling my own after my initial bug report was ignored.
>
> Karl
>
>
> On Mon, Feb 22, 2016 at 1:01 PM Karl MacMillan 
> wrote:
>
>> On Feb 22, 2016, at 3:44 PM, 'Jon Parrott' via Google App Engine <
>> google-appengine@googlegroups.com> wrote:
>>
>> Are there plans to port over NDB for datastore access on managed VMs?
>>>
>>
>> There is on-going discussion about NDB for Cloud Datastore here
>> .
>> The tl;dr is that basically it's possible, it's planned, but its contingent
>> on the next release of the Cloud Datastore API and decoupling NDB from the
>> App Engine SDK.
>>
>>
>> Great.
>>
>> That being said, you can absolutely continue use NDB in Managed VMs by
>> using runtime: python-compat
>> 
>> .
>>
>>
>> Is that new? Last I looked I believe NDB was not supported. If I could
>> suggest it would be helpful to use more specific terminology than Datastore
>> on that page.
>>
>> Is webapp2 going to be deprecated
>>>
>>
>> There are no present plans that I'm aware of to deprecate webapp2.
>> Because webapp2 is a WSGI-compliant web framework and is not itself tied to
>> App Engine, you can use it in Standard, Managed VMs, and pretty much
>> anywhere else. It'll continue to work everywhere WSGI works.
>>
>>
>> Sure - I currently use it on GCE as well just to not use two frameworks.
>> But it is abandoned as far as I can tell - there are bugs that have not
>> been addressed in years.
>>
>> It's also an open-source project and patches are always welcome.
>>
>>
>> I’m sorry, but that’s a little disingenuous. As far as I can tell there
>> is _no_ activity on webapp2. I submitted a bug report that pointed to an
>> exact line of code that needed to be changed but there was no response (
>> https://code.google.com/archive/p/webapp-improved/issues/102). It’s not
>> clear that there is any process to submit patches (contributing on the
>> website has no information -
>> https://webapp-improved.appspot.com/#contribute), there is no active
>> mailing list / discussion forum, the bug tracker is just an archive on
>> google code, and I can see no evidence that there is anyone other than a
>> Google employee that can commit.
>>
>> So - I’ll call your bluff. Tell me how to submit a patch for the issue I
>> pointed to and I’ll happily do so.
>>
>> Otherwise, please consider declaring that the project is abandoned and
>> stop pointing people to webapp2 in App Engine documentation since it’s a
>> dead end.
>>
>> Karl
>>
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, 

Re: [google-appengine] New App Engine Managed VM Docs

[Karl MacMillan]

> On Feb 22, 2016, at 4:14 PM, 'Jon Parrott' via Google App Engine 
>  wrote:
> 
> > Is that new? Last I looked I believe NDB was not supported. If I could 
> > suggest it would be helpful to use more specific terminology than Datastore 
> > on that page.
> 
> It's not new as far as I know - ndb and db have traditionally be the way to 
> access datastore in App Engine, so it's somewhat implied. I'll see if I can't 
> make the docs a bit more clear there.
> 

Hmm - maybe I was wanting ndb in a non-compat python runtime. It’s been a while.

> > So - I’ll call your bluff. Tell me how to submit a patch for the issue I 
> > pointed to and I’ll happily do so.
> 
> You make some excellent points. I will move webapp2 to github, take ownership 
> of it, and I'll be happy to review and merge your patch as well as publish a 
> new version of webapp2 to PyPI. This process takes some time, so I will 
> update this list once that is done.
> 

Hah - fair enough. I’ll send you that patch when you’re ready.

BUT - if you ask me, you really should just put webapp2 into maintenance only 
mode and suggest people move on. There are no advantages over more popular 
frameworks and plenty of downsides.

One note - last I looked much of the session handling code was completely 
broken (https://webapp-improved.appspot.com/api/webapp2_extras/sessions.html 
). I 
ended up just rolling my own after my initial bug report was ignored.

Karl

> 
> On Mon, Feb 22, 2016 at 1:01 PM Karl MacMillan  > wrote:
>> On Feb 22, 2016, at 3:44 PM, 'Jon Parrott' via Google App Engine 
>> > > wrote:
>> 
>> Are there plans to port over NDB for datastore access on managed VMs?
>> 
>> There is on-going discussion about NDB for Cloud Datastore here 
>> .
>>  The tl;dr is that basically it's possible, it's planned, but its contingent 
>> on the next release of the Cloud Datastore API and decoupling NDB from the 
>> App Engine SDK.
>> 
> 
> Great.
> 
>> That being said, you can absolutely continue use NDB in Managed VMs by using 
>> runtime: python-compat 
>> .
>>  
>> 
> 
> Is that new? Last I looked I believe NDB was not supported. If I could 
> suggest it would be helpful to use more specific terminology than Datastore 
> on that page.
> 
>> Is webapp2 going to be deprecated
>> 
>> There are no present plans that I'm aware of to deprecate webapp2. Because 
>> webapp2 is a WSGI-compliant web framework and is not itself tied to App 
>> Engine, you can use it in Standard, Managed VMs, and pretty much anywhere 
>> else. It'll continue to work everywhere WSGI works.
> 
> Sure - I currently use it on GCE as well just to not use two frameworks. But 
> it is abandoned as far as I can tell - there are bugs that have not been 
> addressed in years.
> 
>> It's also an open-source project and patches are always welcome.
>> 
> 
> I’m sorry, but that’s a little disingenuous. As far as I can tell there is 
> _no_ activity on webapp2. I submitted a bug report that pointed to an exact 
> line of code that needed to be changed but there was no response 
> (https://code.google.com/archive/p/webapp-improved/issues/102 
> ). It’s not 
> clear that there is any process to submit patches (contributing on the 
> website has no information - https://webapp-improved.appspot.com/#contribute 
> ), there is no active 
> mailing list / discussion forum, the bug tracker is just an archive on google 
> code, and I can see no evidence that there is anyone other than a Google 
> employee that can commit.
> 
> So - I’ll call your bluff. Tell me how to submit a patch for the issue I 
> pointed to and I’ll happily do so.
> 
> Otherwise, please consider declaring that the project is abandoned and stop 
> pointing people to webapp2 in App Engine documentation since it’s a dead end.
> 
> Karl
> 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Google App Engine" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/google-appengine/HazEmXZRpiw/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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 

Re: [google-appengine] New App Engine Managed VM Docs

['Jon Parrott' via Google App Engine]

> Is that new? Last I looked I believe NDB was not supported. If I could
suggest it would be helpful to use more specific terminology than Datastore
on that page.

It's not new as far as I know - ndb and db have traditionally be the way to
access datastore in App Engine, so it's somewhat implied. I'll see if I
can't make the docs a bit more clear there.

> So - I’ll call your bluff. Tell me how to submit a patch for the issue I
pointed to and I’ll happily do so.

You make some excellent points. I will move webapp2 to github, take
ownership of it, and I'll be happy to review and merge your patch as well
as publish a new version of webapp2 to PyPI. This process takes some time,
so I will update this list once that is done.


On Mon, Feb 22, 2016 at 1:01 PM Karl MacMillan  wrote:

> On Feb 22, 2016, at 3:44 PM, 'Jon Parrott' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
> Are there plans to port over NDB for datastore access on managed VMs?
>>
>
> There is on-going discussion about NDB for Cloud Datastore here
> .
> The tl;dr is that basically it's possible, it's planned, but its contingent
> on the next release of the Cloud Datastore API and decoupling NDB from the
> App Engine SDK.
>
>
> Great.
>
> That being said, you can absolutely continue use NDB in Managed VMs by
> using runtime: python-compat
> 
> .
>
>
> Is that new? Last I looked I believe NDB was not supported. If I could
> suggest it would be helpful to use more specific terminology than Datastore
> on that page.
>
> Is webapp2 going to be deprecated
>>
>
> There are no present plans that I'm aware of to deprecate webapp2. Because
> webapp2 is a WSGI-compliant web framework and is not itself tied to App
> Engine, you can use it in Standard, Managed VMs, and pretty much anywhere
> else. It'll continue to work everywhere WSGI works.
>
>
> Sure - I currently use it on GCE as well just to not use two frameworks.
> But it is abandoned as far as I can tell - there are bugs that have not
> been addressed in years.
>
> It's also an open-source project and patches are always welcome.
>
>
> I’m sorry, but that’s a little disingenuous. As far as I can tell there is
> _no_ activity on webapp2. I submitted a bug report that pointed to an exact
> line of code that needed to be changed but there was no response (
> https://code.google.com/archive/p/webapp-improved/issues/102). It’s not
> clear that there is any process to submit patches (contributing on the
> website has no information -
> https://webapp-improved.appspot.com/#contribute), there is no active
> mailing list / discussion forum, the bug tracker is just an archive on
> google code, and I can see no evidence that there is anyone other than a
> Google employee that can commit.
>
> So - I’ll call your bluff. Tell me how to submit a patch for the issue I
> pointed to and I’ll happily do so.
>
> Otherwise, please consider declaring that the project is abandoned and
> stop pointing people to webapp2 in App Engine documentation since it’s a
> dead end.
>
> Karl
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/HazEmXZRpiw/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/AF77E164-0058-455F-9679-87FDB89C1926%40strajillion.com
> 
> .
> For more options, visit 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/CAN6JEymD%2BEv3jnS7KRr6UN4zBwaHVogNuPrA78Wnq2%2B%2BXV%2B6TA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Domain pointing issue

['Josh Moore' via Google App Engine]

If I access http://appid.appspot.com/, it throws me a redirect to
/sample/course?use_last_location=true.  The redirect then throws an HTTP
404.  From what I can see myself, this is consistent between appspot.com
address and the custom domain address.  The 404 error page also appears to
be a custom one?  So it's hitting your app and being processed by app code,
at some level.

Potentially, there's an auth layer in your code that's preventing the
access for me, and not for you.  Perhaps that's failing on the custom
domain, as well.

On Mon, Feb 22, 2016 at 12:51 PM, Andrei Kamarouski 
wrote:

> appspot is ok. custom domain not. i replaced always with optional in
> secure handlers records (from support article it does seem relevant choice
> too). does it cause errors?
>
> On Monday, February 22, 2016 at 11:45:36 PM UTC+3, joshuamo wrote:
>>
>> 404 also occurs if you go to the appspot.com URL for your app, so this
>> would be an issue in code or app.yaml configuration.
>>
>> On Mon, Feb 22, 2016 at 11:47 AM, Andrei Kamarouski 
>> wrote:
>>
>>> Ok. Seems redirect is gone. But now I get – Unable to access requested
>>> page. HTTP status code: 404.
>>>
>>> --
>>> 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-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@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/02f99b3c-25b3-4a64-8be5-e0c70351a55a%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Josh Moore |  Cloud Solutions Engineer |  josh...@google.com |
>>
> --
> 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/5ca1dc7f-fada-4b2e-b866-3efec13144f6%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Josh Moore |  Cloud Solutions Engineer |  joshu...@google.com |

-- 
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/CAOvpJmVRgWGFGKvu-h4oQbdcLJ6sF1nVi2-xSLjiKEXqGe%2Bupw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New App Engine Managed VM Docs

[Karl MacMillan]

> On Feb 22, 2016, at 3:44 PM, 'Jon Parrott' via Google App Engine 
>  wrote:
> 
> Are there plans to port over NDB for datastore access on managed VMs?
> 
> There is on-going discussion about NDB for Cloud Datastore here 
> .
>  The tl;dr is that basically it's possible, it's planned, but its contingent 
> on the next release of the Cloud Datastore API and decoupling NDB from the 
> App Engine SDK.
> 

Great.

> That being said, you can absolutely continue use NDB in Managed VMs by using 
> runtime: python-compat 
> .
>  
> 

Is that new? Last I looked I believe NDB was not supported. If I could suggest 
it would be helpful to use more specific terminology than Datastore on that 
page.

> Is webapp2 going to be deprecated
> 
> There are no present plans that I'm aware of to deprecate webapp2. Because 
> webapp2 is a WSGI-compliant web framework and is not itself tied to App 
> Engine, you can use it in Standard, Managed VMs, and pretty much anywhere 
> else. It'll continue to work everywhere WSGI works.

Sure - I currently use it on GCE as well just to not use two frameworks. But it 
is abandoned as far as I can tell - there are bugs that have not been addressed 
in years.

> It's also an open-source project and patches are always welcome.
> 

I’m sorry, but that’s a little disingenuous. As far as I can tell there is _no_ 
activity on webapp2. I submitted a bug report that pointed to an exact line of 
code that needed to be changed but there was no response 
(https://code.google.com/archive/p/webapp-improved/issues/102 
). It’s not clear 
that there is any process to submit patches (contributing on the website has no 
information - https://webapp-improved.appspot.com/#contribute 
), there is no active mailing 
list / discussion forum, the bug tracker is just an archive on google code, and 
I can see no evidence that there is anyone other than a Google employee that 
can commit.

So - I’ll call your bluff. Tell me how to submit a patch for the issue I 
pointed to and I’ll happily do so.

Otherwise, please consider declaring that the project is abandoned and stop 
pointing people to webapp2 in App Engine documentation since it’s a dead end.

Karl


-- 
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/AF77E164-0058-455F-9679-87FDB89C1926%40strajillion.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Domain pointing issue

[Andrei Kamarouski]

appspot is ok. custom domain not. i replaced always with optional in secure 
handlers records (from support article it does seem relevant choice too). 
does it cause errors? 

On Monday, February 22, 2016 at 11:45:36 PM UTC+3, joshuamo wrote:
>
> 404 also occurs if you go to the appspot.com URL for your app, so this 
> would be an issue in code or app.yaml configuration.
>
> On Mon, Feb 22, 2016 at 11:47 AM, Andrei Kamarouski  > wrote:
>
>> Ok. Seems redirect is gone. But now I get – Unable to access requested 
>> page. HTTP status code: 404. 
>>
>> -- 
>> 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-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@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/02f99b3c-25b3-4a64-8be5-e0c70351a55a%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Josh Moore |  Cloud Solutions Engineer |  josh...@google.com 
>  |  
>

-- 
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/5ca1dc7f-fada-4b2e-b866-3efec13144f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Domain pointing issue

['Josh Moore' via Google App Engine]

404 also occurs if you go to the appspot.com URL for your app, so this
would be an issue in code or app.yaml configuration.

On Mon, Feb 22, 2016 at 11:47 AM, Andrei Kamarouski 
wrote:

> Ok. Seems redirect is gone. But now I get – Unable to access requested
> page. HTTP status code: 404.
>
> --
> 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/02f99b3c-25b3-4a64-8be5-e0c70351a55a%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Josh Moore |  Cloud Solutions Engineer |  joshu...@google.com |

-- 
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/CAOvpJmXA0dKaZGUcJk2JNRsJA%2ByBgMJpicMduo5eg4%2BWX6Cx%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New App Engine Managed VM Docs

['Jon Parrott' via Google App Engine]

>
> Are there plans to port over NDB for datastore access on managed VMs?
>

There is on-going discussion about NDB for Cloud Datastore here 
.
 
The tl;dr is that basically it's possible, it's planned, but its contingent 
on the next release of the Cloud Datastore API and decoupling NDB from the 
App Engine SDK.

That being said, you can absolutely continue use NDB in Managed VMs by 
using runtime: python-compat 

. 

Is webapp2 going to be deprecated
>

There are no present plans that I'm aware of to deprecate webapp2. Because 
webapp2 is a WSGI-compliant web framework and is not itself tied to App 
Engine, you can use it in Standard, Managed VMs, and pretty much anywhere 
else. It'll continue to work everywhere WSGI works. It's also an 
open-source project and patches are always welcome.

The choice of Flask for our samples in Managed VMs is to more closely match 
the broader Python community. In that same effort, we're also creating 
Django samples.

 only went with it because I thought it would be better supported, but it 
> is far from the best option and not even maintained as far as I can tell. I 
> absolutely think you should push Flask or something similar and just 
> publicly declare that you won’t be maintaining webapp2.
>

We're recommending developers use what they are comfortable and familiar 
with and we're working to make sure that common tools and frameworks work 
on our platform.

On Monday, February 22, 2016 at 11:50:40 AM UTC-8, Karl MacMillan wrote:
>
>
> On Feb 22, 2016, at 1:18 PM, 'Amir Rouzrokh' via Google App Engine <
> google-a...@googlegroups.com > wrote:
>
> Hi everyone,
>
> I’m one of App Engine’s Product Managers and we’ve just pushed out a new 
> iteration of our App Engine Managed VM docs located at 
>
> https://cloud.google.com/appengine/docs/managed-vms/
>
>
> 1. Are there plans to port over NDB for datastore access on managed VMs?
> 2. Is webapp2 going to be deprecated?
>
> I ask because both of those seem to not be getting much attention with the 
> Managed VM transition. It’s particularly concerning to me because I used 
> both webapp2 and NDB as those were the defaults presented in the App Engine 
> documentation for python (and still are). But now I see no signs of NDB 
> moving to Managed VMs and you are using Flask in these examples.
>
> FWIW - I don’t have a preference about about NDB vs. the new datastore API 
> in gcloud except that I have lots of NDB code that I don’t really want to 
> port. As for webapp2 - I feel really burned by that choice. I only went 
> with it because I thought it would be better supported, but it is far from 
> the best option and not even maintained as far as I can tell. I absolutely 
> think you should push Flask or something similar and just publicly declare 
> that you won’t be maintaining webapp2.
>
> Karl
>
>

-- 
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/6aa82639-149b-4915-a19b-f50f08953e7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: will file change Or create by user lost in gae?

['Nicholas (Google Cloud Support)' via Google App Engine]

Thank you for sharing your question here. I'm afraid I'm uncertain what you 
mean by your question.

   - Is your question about the principles and applications of stateless 
   design?
   - If so, are there more specific questions or examples for which you'd 
   like answers?
   - If not, could you explain question with little more detail?
   

On Wednesday, February 17, 2016 at 5:31:37 AM UTC-5, Jasper Lai wrote:
>
> Referring to 
> https://www.otreva.com/blog/deploying-wordpress-amazon-web-services-aws-ec2-rds-via-elasticbeanstalk/
>
> Aws beanstalk has this issue. Is gae the same?
>

-- 
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/156b2647-95d3-4b5a-8f30-da68ff1242e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New App Engine Managed VM Docs

[Karl MacMillan]

> On Feb 22, 2016, at 1:18 PM, 'Amir Rouzrokh' via Google App Engine 
>  wrote:
> 
> Hi everyone,
> 
> I’m one of App Engine’s Product Managers and we’ve just pushed out a new 
> iteration of our App Engine Managed VM docs located at 
> 
> https://cloud.google.com/appengine/docs/managed-vms/ 
> 
> 

1. Are there plans to port over NDB for datastore access on managed VMs?
2. Is webapp2 going to be deprecated?

I ask because both of those seem to not be getting much attention with the 
Managed VM transition. It’s particularly concerning to me because I used both 
webapp2 and NDB as those were the defaults presented in the App Engine 
documentation for python (and still are). But now I see no signs of NDB moving 
to Managed VMs and you are using Flask in these examples.

FWIW - I don’t have a preference about about NDB vs. the new datastore API in 
gcloud except that I have lots of NDB code that I don’t really want to port. As 
for webapp2 - I feel really burned by that choice. I only went with it because 
I thought it would be better supported, but it is far from the best option and 
not even maintained as far as I can tell. I absolutely think you should push 
Flask or something similar and just publicly declare that you won’t be 
maintaining webapp2.

Karl

-- 
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/15C0945B-A4B5-4336-8F9E-80B6C9E61BAA%40strajillion.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Domain pointing issue

[Andrei Kamarouski]

Ok. Seems redirect is gone. But now I get – Unable to access requested 
page. HTTP status code: 404. 

-- 
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/02f99b3c-25b3-4a64-8be5-e0c70351a55a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Domain pointing issue

['Josh Moore' via Google App Engine]

Zeehad is correct here.  The curl output, for reference:

$ curl -I http://courses.reframe.space
HTTP/1.1 302 Found
Location: https://courses.reframe.space/
Date: Mon, 22 Feb 2016 18:17:06 GMT
Content-Type: text/html
Server: Google Frontend
Transfer-Encoding: chunked


On Mon, Feb 22, 2016 at 10:09 AM, Andrei Kamarouski 
wrote:

> I don't need SSL at the moment.
>
> On Monday, February 22, 2016 at 9:04:54 PM UTC+3, joshuamo wrote:
>>
>> Your second screenshot shows that no certificates have been uploaded.
>> You should follow the documentation starting from here:
>> https://cloud.google.com/appengine/docs/java/console/using-custom-domains-and-ssl#adding_ssl_to_your_custom_domain
>>
>> On Mon, Feb 22, 2016 at 9:52 AM, 'Zeehad (Cloud Platform Support)' via
>> Google App Engine  wrote:
>>
>>> Can you post the app.yaml showing how you're handling URLs?
>>>
>>> --
>>> 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-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@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/9c8ae334-b1a6-4de2-b867-deb3045cfd8c%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Josh Moore |  Cloud Solutions Engineer |  josh...@google.com |
>>
> --
> 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/c481bbff-5eff-45cc-8fb5-81e8d463c07e%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Josh Moore |  Cloud Solutions Engineer |  joshu...@google.com |

-- 
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/CAOvpJmVj7qUENO_ZJYvYGO%2BLk%2Bb9kEj%2BDZ_OD9MJsam5d7f%2BTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] New App Engine Managed VM Docs

['Amir Rouzrokh' via Google App Engine]

Hi everyone,

I’m one of App Engine’s Product Managers and we’ve just pushed out a new 
iteration of our App Engine Managed VM docs located at 

https://cloud.google.com/appengine/docs/managed-vms/

Give it a try please and send over feedback including any more developer 
guides you would like to see, any errors, etc. The feedback button is on 
the top right hand side of every page. Thanks in advance!

-- 
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/e37f9979-857b-4f62-afa8-7392bb58aec6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Domain pointing issue

['Zeehad (Cloud Platform Support)' via Google App Engine]

In your app.yaml, it looks like you're auto-redirecting to HTTPS URL on 
different handlers using the following.

secure: always


Since you've mentioned, you do no need SSL at the moment; Setting the 
values to 'never' should make sure it doesn't redirect to HTTPs 
automatically. See this article 

 
for more information.

-- 
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/b8c40d76-aeab-4493-ba54-6d1633e283c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Domain pointing issue

[Andrei Kamarouski]

I don't need SSL at the moment. 

On Monday, February 22, 2016 at 9:04:54 PM UTC+3, joshuamo wrote:
>
> Your second screenshot shows that no certificates have been uploaded.  You 
> should follow the documentation starting from here: 
> https://cloud.google.com/appengine/docs/java/console/using-custom-domains-and-ssl#adding_ssl_to_your_custom_domain
>
> On Mon, Feb 22, 2016 at 9:52 AM, 'Zeehad (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Can you post the app.yaml showing how you're handling URLs?
>>
>> -- 
>> 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-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@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/9c8ae334-b1a6-4de2-b867-deb3045cfd8c%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Josh Moore |  Cloud Solutions Engineer |  josh...@google.com 
>  |  
>

-- 
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/c481bbff-5eff-45cc-8fb5-81e8d463c07e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Domain pointing issue

[Andrei Kamarouski]

That's one I have uploaded to appspot project. 

On Monday, February 22, 2016 at 8:52:55 PM UTC+3, Zeehad (Cloud Platform 
Support) wrote:
>
> Can you post the app.yaml showing how you're handling URLs?
>

-- 
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/d3cc8643-2106-4f52-b865-f4421d73f245%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


app.yaml
Description: Binary data

Re: [google-appengine] Re: Domain pointing issue

['Josh Moore' via Google App Engine]

Your second screenshot shows that no certificates have been uploaded.  You
should follow the documentation starting from here:
https://cloud.google.com/appengine/docs/java/console/using-custom-domains-and-ssl#adding_ssl_to_your_custom_domain

On Mon, Feb 22, 2016 at 9:52 AM, 'Zeehad (Cloud Platform Support)' via
Google App Engine  wrote:

> Can you post the app.yaml showing how you're handling URLs?
>
> --
> 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/9c8ae334-b1a6-4de2-b867-deb3045cfd8c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Josh Moore |  Cloud Solutions Engineer |  joshu...@google.com |

-- 
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/CAOvpJmVOxzay%3Dw25gNO-YFf2G1iiJRaJ%2BD7W7bZPyxpD%2BvJNkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Domain pointing issue

['Zeehad (Cloud Platform Support)' via Google App Engine]

Can you post the app.yaml showing how you're handling URLs?

-- 
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/9c8ae334-b1a6-4de2-b867-deb3045cfd8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Asynchronous Deployment With Java AppEngine SDK

['Andrew Teall' via Google App Engine]

Hi,
We're trying to deploy multiple modules and managed VMs using the Java 
AppEngine SDK. We are currently using a script with a  for loop that 
backgrounds each call to the appcfg.sh and waiting 30 seconds between 
starting each deploy. However we see 409 conflicts pretty often. Is there a 
better way to accomplish this or does anyone have any experience getting 
this to work with 100% success.

Thanks,
Andrew

-- 
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/9fe39c67-a5fc-4e73-af68-53823cc2773f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Cron job not running on HTTPS

[Akash Patni]

Hi all,

I am working on django project which is deployed on Google app engine. 
Currently I have enabled the functionality of forced redirection over SSL 
on website. After enabling forced redirection of website over SSL cron jobs 
are getting failed. Cron jobs are running fine over HTTP. Does anyone have 
clue over this issue.Thanks in advance

-- 
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/0b6eb182-3556-4047-8807-7b670437dcbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.