[google-appengine] Re: GAE Microservices

['Andrew Cooper' via Google App Engine]

Which documentation are you following? Are you thinking of using GAE Flex 
or GAE Standard?

I have added a couple of links that you might find interesting that details 
how requests are routed in GAE. Please note, this is for Python but the 
concept is the same for other languages.

   - 
   
   How Requests are Routed 
   

   - 
   
   Communicating Between Your Services 
   

   - 
   
   Serverless network endpoint groups overview 
   
   

On Monday, April 12, 2021 at 11:54:36 AM UTC+2 optimum...@gmail.com wrote:

> Hi
>
> I am trying to develop an GAE with multiple modules each having distinct 
> codes talking to Firebase.  A client might need an app with only 2 modules 
> and other might need 5 modules...i was hoping to load them as services or 
> microservices...problem is how to connect them together ?
>
> It is like going to an accounting system and having a GL, Job Costing, 
> Project costing as a separate module.  In the main entry point  (services: 
> default) there will be a button to go to each services or modules  From 
> what i understand in the documentation...each services (previously modules) 
> cannot access to each of them unless via REST.
>
> Any bright ideas how to do it in GAE using Firebase ?
>
> Appreciate the input.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6699ef9b-0b1c-4986-b602-61d8965b802en%40googlegroups.com.

[google-appengine] Re: GAE MIcroServices

['Andrew Cooper' via Google App Engine]

Which documentation are you following? Are you thinking of using GAE Flex 
or GAE Standard? 

I have added a couple of links that you might find interesting that details 
how requests are routed in GAE. Please note, this is for Python but the 
concept is the same for other languages. 

   - How Requests are Routed 
   

   
   

   - Communicating Between Your Services 
   

   - Serverless network endpoint groups overview 
   
   

On Monday, April 12, 2021 at 11:54:38 AM UTC+2 optimum...@gmail.com wrote:

> Hi
>
> Similar to an accounting software with multiple modules each with distinct 
> codes and data access...is there any way of using GAE services (or 
> microservices or prev modules) as modules all linked to a "default" (in 
> app.yaml) module ?  The documentation seems to suggest that each services 
> are distinct and cannot be linked unless via REST.
>
> Any input is appreciated.
>
> Thanks
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/342b3e4a-9497-4208-a095-7d84204b5b96n%40googlegroups.com.

[google-appengine] Re: Cloud Run services latency spikes

['Andrew Cooper' via Google App Engine]

If you believe this is an internal issue while using Cloud Run in 
`europe-west-1b` that is causing spikes to your application every six 
months you can raise this on our Cloud Run issue tracker 
 page 
for further investigation. We will review the issue to see if this is 
something that is affecting all users.

On Tuesday, April 20, 2021 at 8:33:05 AM UTC+2 Andreas Lans wrote:

> This happens approximatly every six months on our installations, that some 
> internal problem leads to long spikes. Do we as customers need to factor in 
> the cost of having a constantly running support subscription when choosing 
> between Google Cloud and other vendors? Or is there some way to contact 
> Google Support for these types of problems without paying? Seems pretty 
> strange that we should have costs for notifying Google of internal problems 
> that we have no way to monitor without a payed subscription? 
>
> måndag 19 april 2021 kl. 20:42:40 UTC+2 skrev wus...@google.com:
>
>>
>> I believe the best way is to file the support case in the cloud console, 
>> in this way the Support team can have a deeper look into the issue.
>>
>>
>> On Monday, April 19, 2021 at 11:10:40 AM UTC-4 Andreas Lans wrote:
>>
>>> Hello!
>>>
>>> We have several projects in Google Cloud and we have recurring problems 
>>> with latency spikes reaching the databases in our respective projects (the 
>>> projects that are effected are the ones in europe-west-1b. 
>>>
>>> Not all services in cloud run are affected but at least half of them in 
>>> this project for example. These services have been working for several 
>>> months have not been recently redeployed, yet we constantly get these 
>>> spikes. 
>>>
>>> I cant find anything regarding a lack of resources for services or for 
>>> the database, what can be done to remedy this? 
>>>
>>> Do we need to pay for support by Google, if so, where can you see the 
>>> status on issues like this without paying for support? [image: 
>>> Screenshot 2021-04-19 at 14.47.18.png]
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/06d52578-98cb-4907-8e24-1e6ea956ca71n%40googlegroups.com.

[google-appengine] Re: Cloud Run services latency spikes

['Andrew Cooper' via Google App Engine]

If you believe this is an internal issue while using Cloud Run in 
`europe-west-1b` that is causing spikes to your application every six 
months you can raise this on our [Cloud Run issue 
tracker](https://issuetracker.google.com/issues/new?component=608076=0)
 
page for further investigation. We will review the issue to see if this is 
something that is affecting all users.

On Tuesday, April 20, 2021 at 8:33:05 AM UTC+2 Andreas Lans wrote:

> This happens approximatly every six months on our installations, that some 
> internal problem leads to long spikes. Do we as customers need to factor in 
> the cost of having a constantly running support subscription when choosing 
> between Google Cloud and other vendors? Or is there some way to contact 
> Google Support for these types of problems without paying? Seems pretty 
> strange that we should have costs for notifying Google of internal problems 
> that we have no way to monitor without a payed subscription? 
>
> måndag 19 april 2021 kl. 20:42:40 UTC+2 skrev wus...@google.com:
>
>>
>> I believe the best way is to file the support case in the cloud console, 
>> in this way the Support team can have a deeper look into the issue.
>>
>>
>> On Monday, April 19, 2021 at 11:10:40 AM UTC-4 Andreas Lans wrote:
>>
>>> Hello!
>>>
>>> We have several projects in Google Cloud and we have recurring problems 
>>> with latency spikes reaching the databases in our respective projects (the 
>>> projects that are effected are the ones in europe-west-1b. 
>>>
>>> Not all services in cloud run are affected but at least half of them in 
>>> this project for example. These services have been working for several 
>>> months have not been recently redeployed, yet we constantly get these 
>>> spikes. 
>>>
>>> I cant find anything regarding a lack of resources for services or for 
>>> the database, what can be done to remedy this? 
>>>
>>> Do we need to pay for support by Google, if so, where can you see the 
>>> status on issues like this without paying for support? [image: 
>>> Screenshot 2021-04-19 at 14.47.18.png]
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b3175d27-cefd-406a-8e8f-f3793be42440n%40googlegroups.com.

[google-appengine] Re: App Engine microservices + IAP + API Gateway

['Andrew Cooper' via Google App Engine]

I would suggest that you go through a few debug steps to see where it might 
have failed. Typically it is because you missed a step during the 
configuration.

   1. 
   
   Make sure the API are enabled
   
Re-enabling the APIs might seem obvious, but you can re-enable the APIs 
with the debug flag. They might have failed silently and did not enable as 
expected. Try again with the debug flag to identify any potential root 
causes.
```
gcloud services list 

```

Required APIs

   - 
   
   iap.googleapis.com // Cloud Identity-Aware Proxy API
   - 
   
   apigateway.googleapis.com // API Gateway API
   - 
   
   servicemanagement.googleapis.com // Service Management API
   - 
   
   servicecontrol.googleapis.com // Service Control API
   
```
gcloud services enable  --log-http --verbosity=debug 

```

Please note, do not share the output of this command unless you redact any 
identifiable information first.

   1. 
   
   Make sure you have set up IAP access correctly
   
Requests from the API Gateway to any back-end service will most likely use 
authentication. These requests are secured using OpenID Connect (OIDC) 
tokens signed by the gateway's service account.

Check to see if your back-end services can accept OIDC tokens for 
authentication and authorization 1 
.

Although you have added the IAP-secured Web App User permission to the 
service account, as per the documentation 2 
, you 
also need to add the permission to the Project Owner.

*Role-based access: If you're a project owner, you may think that you get 
automatic access to the app. That is not the case as only accounts with the 
IAP-secured Web App User role on this project will be given access. Imagine 
you're in corporate IT implementing IAP access to the HR payroll system. In 
most scenarios, only the staff on the Payroll team should have access to 
the app. This is one of the reasons why role-based access is more secure. 
The owner (or editor, etc.) of a project can manage all aspects of the 
project but doesn't automatically get app access.*

On Friday, February 26, 2021 at 12:27:10 PM UTC+1 du...@nolte.io wrote:

> Hello,
>
> I'm using API Gateway for different App Engine microservices, I'm 
> following the tutorial here 
>  but 
> when I turn on the IAP for App Engine and I try to make a request through 
> the Gateway, I get a redirection response. If I test this through the 
> browser, I login with my google account and I see the response. But If I 
> test this through Postman or curl, I don't get any results.
>
> The documentation says that  *To grant access to your App Engine app, you 
> will need to configure a service account 
> 
>  with 
> the correct permissions for your API Gateway. *
> I added the permission "IAP-secured Web App User" to the service account 
> used for the gateway.
>
> I thought that the API Gateway should handle the authentication part and I 
> could access to the App Engine endpoint. 
>
> What is the correct behavior of the IAP - API Gateway configuration?
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6ec059ce-9946-4ec9-9abe-8b4c7dc407can%40googlegroups.com.

[google-appengine] Re: How does GCP decides when a Kubernetes deployment is completed

['Andrew Cooper' via Google App Engine]

You will find this documentation 

 interesting 
as it advises how to implement and configure "readiness and startup" probes 
for your containers. The "liveness" probe can check a container or when an 
application has stalled and does not accept traffic. This approach can be 
customised to suit your requirements rather than relying on a general catch 
all signal.
On Monday, April 5, 2021 at 5:42:20 AM UTC+2 luca...@icloud.com wrote:

> Hi There,
>
> I have a few Java microservices and when I redeploy them, one of them 
> needs like 40 seconds after starting up (it's a dropwizard application) to 
> load data and do some computation to actually be ready to serve requests. 
> This extra time makes so GCP thinks the service is ready and keeps 
> deploying other instances and when the service receives requests they fail.
>
> How does GCP determins that a Kubernetes app is ready to serve request? Is 
> there a way to prologue the deployment state or tell GCP that it's not 
> finished until say, an API returns a 200?
>
> Thanks
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7e4bf3e0-60b6-45eb-8428-5a977438ea7cn%40googlegroups.com.

Re: [google-appengine] Re: Exceeded soft memory limit - how to configure app.yaml for java 11

['Andrew Cooper' via Google App Engine]

Do you know how much memory it uses when you run it locally? 

Increasing the size of the instance is not generally the best approach. For 
example, if you have a memory leak, then the instance size might need to 
grow exponentially!!

You can use Cloud Code  to help you debug 
 these types of 
situations. You can also use the Cloud Profiler for Java 
 to understand 
better what your code is consuming.

I am more familiar with Python than Java, but I wonder how you are 
implementing the Java code? Looping in Python is notoriously problematic as 
it has a habit of leaving behind and accumulating "garbage" in memory. You 
can implement List Comprehensions, Generators, and Yield returns in Python 
to consume memory more efficiently. I have added a link that explains my 
thinking better and provides a helpful comparison 
.
 
I believe that you can do something similar in Java 
, but I might 
be wrong. You can also try chunking your data, but you might be limited in 
how you can split your data, so it might not be the best fit.
On Saturday, March 27, 2021 at 8:33:52 AM UTC+1 ra wrote:

> Thanks Ludo!
> I have zero idea how this is implemented internally
> - but might it be the case that the VPN connector uses a substantial
> amount of memory of the instance?
>
>
> On Thu, Mar 25, 2021 at 10:20 PM Ludovic Champenois
>  wrote:
> >
> >
> > Hi,
> > I am not sure JAVA_TOOL_OPTIONS is supported (nor documented) for GAE 
> Java11..
> > You have a few options:
> > 1/ either move to
> > instance_class: F4
> > or
> > instance_class: F2
> >
> > to get bigger instances.
> > Or manually control your entrypoint... I assume you deployed a jar, 
> let's call it myjar.jar
> >
> > the default entrypoint generated is:
> > java -jar myjar.jar
> >
> > You can change it by adding this to your app.yaml:
> >
> > entrypoint: java -XX:MaxRAM=200m -Xmx200m -jar myjar.jar
> >
> > Some more doc at 
> https://cloud.google.com/appengine/docs/standard/java11/runtime#application_startup
> >
> > Hope this helps,
> > Ludo
> >
> > On Wednesday, March 24, 2021 at 10:31:54 AM UTC-7 ra wrote:
> >>
> >> Hi,
> >>
> >> I am running in the issue "Exceeded soft memory limit of 256 MB with
> >> 283 MB after servicing 3 requests total.
> >> Consider setting a larger instance class in app.yaml.".
> >>
> >> My app.yaml looks like this:
> >>
> >> 
> >> runtime: java11
> >> instance_class: F1
> >>
> >> env_variables:
> >> JAVA_TOOL_OPTIONS: "-XX:MaxRAM=200m -Xmx200m"
> >> inbound_services:
> >> - warmup
> >>
> >> handlers:
> >> - url: /.*
> >> script: auto
> >> secure: always
> >> redirect_http_response_code: 301
> >>
> >> automatic_scaling:
> >> min_instances: 1
> >> max_instances: 2
> >>
> >> # Connecting to the cloud sql instance via app engine standard needs a
> >> vpc access connector:
> >> # 
> https://stackoverflow.com/questions/51328359/how-to-connect-to-cloud-sql-mysql-database-from-app-engine
> >> vpc_access_connector:
> >> name: 
> "projects/locations/europe-west3/connectors/serverless-connector"
> >> 
> ##
> >>
> >> My question now is: How can I tell the java runtime to NOT use more
> >> than the available RAM of the instance?
> >>
> >> Strangely: Anything I set in terms of -Xmx gets discarded and my app
> >> always has a max heap of 127.729664MB.
> >> So it seems my JAVA_TOOL_OPTIONS do not get picked up by the JVM.
> >>
> >> So where does the rest of the memory go?
> >> Or is this "something else" like the serverless connector in the
> >> container that consumes all the memory?
> >>
> >>
> >> Thanks!
> >>
> >>
> >> Raphael
> >
> > --
> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/55cf6419-9a2b-4fb5-a51d-086d084ade78n%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/54285a1f-2ece-4841-b14d-77fa975e6c2an%40googlegroups.com.

[google-appengine] Re: order of jars on java 8 appengine

['Andrew Cooper' via Google App Engine]

Were you able to find the answer to your question?

The `java.lang.NoClassDefFoundError` is a fairly generic error message and 
can be hard to debug correctly without further context.

It will be good to implement some form of logging 
 for your 
application to help you narrow down the root cause quicker. The advantage 
of implementing logs with your code is that some errors might not cause a 
significant problem until it is too late. This way, you can monitor your 
running code in different situations.

How did you deploy your App? An excellent way to manage your code for App 
Engine is to create a repository 
 and deploy 
an app to App Engine 

 directly 
from the repository. This way, you gain complete control over any changes 
and even automate smoother deployments.

On Wednesday, March 3, 2021 at 6:35:49 AM UTC+1 
rajesh...@veersoftsolutions.com wrote:

> Hello,
> On java 8 appengine app (not local) , is there a way to find out the 
> classpath or the order of jars, the appengine is scanning.
>
> I am getting java.lang.NoClassDefFoundError error for one of my internal 
> class.
>
> I tried downloading the app through the console, but looks like that page 
> is not available anymore.  
> What tools I have to find out what exactly is deployed on to the 
> appengine. 
>
> What log statement can I insert, so that I can get the order or jars or 
> the classpath.
>
> -- 
> Rajesh
> www.servicefolder.com 
> 
> *Field Service Software on Google Cloud Platform and Mobile*
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8187c84f-f2d9-438b-ad46-687c8a173aa0n%40googlegroups.com.

[google-appengine] Re: Best Product/Solution for my requirement

['Andrew Cooper' via Google App Engine]

You have two excellent options here for web development in Python:

   - Django : a high-level Python Web 
   framework for quick development
   - Flask : a micro web 
   framework

Both of these packages work nicely with several different GCP products. 
Personally, I prefer Django because it provides a more comprehensive 
workflow, but it has a steep learning curve. Flask, on the other hand, is 
much more lightweight and works well for small projects. Both options 
provide nice templating that is suitable for the type of website you are 
hoping to develop.

Regarding your infrastructure, a lot will depend on how involved you want 
to get. If you wish to develop websites and host them on GCP, you can look 
at the many different options you have available 
 to you.

The two primary services for dynamic websites are Cloud Run 
 and App Engine 
. If you want to focus on mobile 
development, you can have a look at Firebase Hosting 
. Although it is possible to 
use Python and Firebase 
 to integrate your 
website with a mobile option, the most popular method seems to be using 
Flutter/Dart.

An excellent place to start is to play with some of the available products. 
There is a Cloud Run interactive 

 walk-through 
to get you started and some good Python documentation for App Engine 
. If you want to create a 
Python-specific development environment with GCP, it is good to follow this 
guide to help you get started 
On Thursday, March 25, 2021 at 12:44:39 PM UTC+1 Ooty Beauty wrote:

> Hi,
>
> I'm new to Google Cloud. I'm planning to build a dynamic website with 
> Python and would like to know from the experts what product/solution best 
> suits the requirement given below
>
> I HAVE:
>
>1. Domain registered on domains.google.com
>
>
> I WANT TO:
>
>1. Build a dynamic website with python
>2. Host the website in the cloud as I don't have my own infrastructure
>3. Develop API  for both website and mobile
>4. Store the data in the cloud
>5. My development team to have access to the code
>6. Update the website/API regularly without complication 
>
> Thanks,
> Pradeep
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/96d904da-c944-4b3d-b621-7c657cbbf71en%40googlegroups.com.

[google-appengine] Re: Cloud Functions - safe for a key?

[Andrew Davies]

Thanks @Elliot!

To answer those questions:
- It's entirely possible that I'm using Cloud Functions for a purpose they 
weren't designed for. There are Python scripts I want to run on a scheduled 
basis (once a day) via PubSub which access some data, parse it to a table, 
then load to BigQuery. Using service accounts is an easy way to manage 
authorisation and seem designed for this sort of task. 
- I'm still learning and not sure of the best way to convert a locally 
running script to being cloud based. Security is less of a consideration 
when running locally but I'm aware that storing private keys in plain text 
in a public cloud isn't a great idea, which is why I was curious as to what 
I might need to consider or if my concerns were unfounded.
- Security concerns are that someone may be able to access the plain text 
key file. Again, not that this service account has access to highly 
confidential information, but I like taking reasonable precautions.

I think the method you described should work fine though! Thank you. :)
On Tuesday, 12 January 2021 at 6:20:03 am UTC+10 Elliott (Cloud Platform 
Support) wrote:

> Hello,
>
> I’d like to address your questions but before I do, I would like you to 
> know that there would be no by and large answer on security. It depends on 
> your requirements. Depending on the answers to some questions, I would be 
> guiding you to a point where you may benefit.
>
> To begin, you mentioned that you wish to use a service key to your Cloud 
> Function.
>
> Is there a reason why you chose this approach in that a Cloud Function has 
> a service account?
> Why are you using a Cloud Function to store your key?
> What specific security concerns do you have? 
>
> I was able to look further and was suggested this thread here 
> 
>  
> that has several views that may assist you. Perhaps it may provide you with 
> further insight.
>
> Encrypt your service account credential json file using Cloud KMS/vault 
> and upload it to Cloud Storage.
> Fetch service account credential json file from Cloud Storage and decrypt 
> it using a Cloud KMS service account which has encrypt/decrypt permission.
> Parse service account credential json file at runtime and get private_key, 
> client_email and ProjectId.
> Pass these three secret variables to the client library
> We must not store secret things like plain text, e.g cloud function 
> environment variables.
>
> I hope this helps.
>
>
> On Monday, January 11, 2021 at 9:16:31 AM UTC-5 ajdav...@gmail.com wrote:
>
>> Hi there,
>>
>> I'm pretty new so please pardon if this is a stupid question. I seem to 
>> get led astray when looking for security info too. 
>>
>> Is it safe to store a key as part of a package published to Google Cloud 
>> Functions? Specifically this would be a key used for a Google service 
>> account as part of a GCP project. 
>>
>> If not natively, is there anything I could do to make it 'safe' or is it 
>> generally a bad idea all around?
>>
>> Nothing super sensitive to be done by the function but still would prefer 
>> it to run with minimal risk of interference. 
>>
>> Thanks!
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/48f68a9d-7c6a-402f-ba4e-6c6a1febb808n%40googlegroups.com.

[google-appengine] Re: What's the best way to keep Requirements up-to-date?

['Andrew Cooper' via Google App Engine]

You're welcome. If you have any other questions let us know,
On Monday, January 11, 2021 at 2:49:20 PM UTC+1 Alex wrote:

> Very interesting thank you!
>
> On Friday, January 8, 2021 at 5:08:04 PM UTC+1 anco...@google.com wrote:
>
>> Managing dependencies can be tricky! You might want to check Pipenv as 
>> suggested above as it acts as a package and virtual environment management 
>> tool. It also uses a [Pipfile][1] and a [Pipfile.lock][2] rather than a 
>> requirments.txt file. The advantage of a Pipfile is it will be more 
>> accommodating semantically regarding how you declare your versions. For 
>> example, `pipenv install requests~=1.2` will install version 1.2 and any 
>> minor update, but not 2.0. You can also specify a hash to the 
>>
>> ```
>> $ pipenv install "requests>=1.4"   # install a version equal or larger 
>> than
>> $ pipenv install "requests<=2.13"  # install a version equal or lower
>> $ pipenv install "requests>2.19"   # install 2.19.1 but not 2.19.0
>> ```
>>
>> You can specify `pipenv install -r requirements.txt` to import a 
>> requirements file and create the Pipfile. If you want to upgrade all 
>> packages, you can just run `pipenv update`.
>>
>> [1]: https://github.com/pypa/pipfile
>> [2]: 
>> https://pipenv.pypa.io/en/latest/basics/#example-pipfile-pipfile-lock
>>
>> On Friday, January 8, 2021 at 10:24:00 AM UTC+1 Alex wrote:
>>
>>> I'm on GAE standard but I don't think that makes a difference. The 
>>> thread you share is interesting but goes into the direction of having 
>>> versioned packages in the requirements file for even your dev environment. 
>>>
>>> Trying to be more specific on the workflow I imagine, I would describe 
>>> the following: 
>>> 1- continue to build and deploy my Dev project without versioned 
>>> requirements
>>> 2- when I have a stabilized Dev project build, be able to gather the 
>>> actual package version it was built with. How could I do that even manually?
>>> 3- build staging with a versioned requirements file - versions being 
>>> those gathered at step 2
>>> 4- perform full QA on staging
>>> 5- build prod with a versioned requirements file - versions being those 
>>> gathered at step 2 and those staging QA was performed with
>>>
>>> So a key point seems to be about how can I perform step 2? 
>>>
>>> On Thursday, January 7, 2021 at 4:04:58 PM UTC+1 Elliott (Cloud Platform 
>>> Support) wrote:
>>>
 Hello Alex,

 From your description, you’ve decided not to version your 
 requirements.txt in Python. This is not a crazy approach but there are 
 alternatives. I’m assuming you’re using App Engine Flex. I was able to 
 find 
 a document here 
 
  
 that describes that you do not need to specify a version but indicates why 
 it would work in some cases. The following information that I found highly 
 suggests using a virtual environment in Python.

 It reads:

 Specifying a version is not a requirement though it does help a lot in 
 the future. Some versions of packages will not work well with other 
 packages and their respective versions. It is hard to predict how changes 
 in the future will affect these interrelationships. This is why it is very 
 beneficial to create a snapshot in time (in your requirements.txt) showing 
 which version interrelationships do work.

 There is an approach for best practices in this thread regarding your 
 concern of breaking change in a package update and explains virtual 
 environments:

 it's a good idea to get into the habit of using virtual environments to 
 avoid dependency issues, especially when developing your own stuff. 
 Anaconda offers a simple solution with the conda create command, and 
 virtualenv works great with virtualenvwrapper for a lighter-weight 
 solution. Another solution, pipenv, is quite popular.

 There is further explanation:

 A tip - you should aim to be using a virtual environment for each 
 individual project that you'll be working on. This creates a 'bubble' for 
 you to work within and to install specific package versions in, without it 
 affecting your other projects. It will save you a lot of headaches in the 
 future as your packages and versions will be kept project specific. 

 There is a way in this thread 
 
  
 on how to check if the packages in your requirements.txt are up to date. 
 You may choose to act on them as described.

 $ pip list --outdated

 You have described how you are working with three projects to implement 
 your non-versioning scenario on Google Cloud Platform but I am unclear 
 about your question. Can you tell me more about how you are validating the 
 application and 

[google-appengine] Cloud Functions - safe for a key?

[Andrew Davies]

Hi there,

I'm pretty new so please pardon if this is a stupid question. I seem to get 
led astray when looking for security info too. 

Is it safe to store a key as part of a package published to Google Cloud 
Functions? Specifically this would be a key used for a Google service 
account as part of a GCP project. 

If not natively, is there anything I could do to make it 'safe' or is it 
generally a bad idea all around?

Nothing super sensitive to be done by the function but still would prefer 
it to run with minimal risk of interference. 

Thanks!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e83a0ffc-547f-49fb-8cd0-dc890aaac948n%40googlegroups.com.

[google-appengine] Re: What's the best way to keep Requirements up-to-date?

['Andrew Cooper' via Google App Engine]

Managing dependencies can be tricky! You might want to check Pipenv as 
suggested above as it acts as a package and virtual environment management 
tool. It also uses a [Pipfile][1] and a [Pipfile.lock][2] rather than a 
requirments.txt file. The advantage of a Pipfile is it will be more 
accommodating semantically regarding how you declare your versions. For 
example, `pipenv install requests~=1.2` will install version 1.2 and any 
minor update, but not 2.0. You can also specify a hash to the 

```
$ pipenv install "requests>=1.4"   # install a version equal or larger than
$ pipenv install "requests<=2.13"  # install a version equal or lower
$ pipenv install "requests>2.19"   # install 2.19.1 but not 2.19.0
```

You can specify `pipenv install -r requirements.txt` to import a 
requirements file and create the Pipfile. If you want to upgrade all 
packages, you can just run `pipenv update`.

[1]: https://github.com/pypa/pipfile
[2]: https://pipenv.pypa.io/en/latest/basics/#example-pipfile-pipfile-lock

On Friday, January 8, 2021 at 10:24:00 AM UTC+1 Alex wrote:

> I'm on GAE standard but I don't think that makes a difference. The thread 
> you share is interesting but goes into the direction of having versioned 
> packages in the requirements file for even your dev environment. 
>
> Trying to be more specific on the workflow I imagine, I would describe the 
> following: 
> 1- continue to build and deploy my Dev project without versioned 
> requirements
> 2- when I have a stabilized Dev project build, be able to gather the 
> actual package version it was built with. How could I do that even manually?
> 3- build staging with a versioned requirements file - versions being those 
> gathered at step 2
> 4- perform full QA on staging
> 5- build prod with a versioned requirements file - versions being those 
> gathered at step 2 and those staging QA was performed with
>
> So a key point seems to be about how can I perform step 2? 
>
> On Thursday, January 7, 2021 at 4:04:58 PM UTC+1 Elliott (Cloud Platform 
> Support) wrote:
>
>> Hello Alex,
>>
>> From your description, you’ve decided not to version your 
>> requirements.txt in Python. This is not a crazy approach but there are 
>> alternatives. I’m assuming you’re using App Engine Flex. I was able to find 
>> a document here 
>> 
>>  
>> that describes that you do not need to specify a version but indicates why 
>> it would work in some cases. The following information that I found highly 
>> suggests using a virtual environment in Python.
>>
>> It reads:
>>
>> Specifying a version is not a requirement though it does help a lot in 
>> the future. Some versions of packages will not work well with other 
>> packages and their respective versions. It is hard to predict how changes 
>> in the future will affect these interrelationships. This is why it is very 
>> beneficial to create a snapshot in time (in your requirements.txt) showing 
>> which version interrelationships do work.
>>
>> There is an approach for best practices in this thread regarding your 
>> concern of breaking change in a package update and explains virtual 
>> environments:
>>
>> it's a good idea to get into the habit of using virtual environments to 
>> avoid dependency issues, especially when developing your own stuff. 
>> Anaconda offers a simple solution with the conda create command, and 
>> virtualenv works great with virtualenvwrapper for a lighter-weight 
>> solution. Another solution, pipenv, is quite popular.
>>
>> There is further explanation:
>>
>> A tip - you should aim to be using a virtual environment for each 
>> individual project that you'll be working on. This creates a 'bubble' for 
>> you to work within and to install specific package versions in, without it 
>> affecting your other projects. It will save you a lot of headaches in the 
>> future as your packages and versions will be kept project specific. 
>>
>> There is a way in this thread 
>> 
>>  
>> on how to check if the packages in your requirements.txt are up to date. 
>> You may choose to act on them as described.
>>
>> $ pip list --outdated
>>
>> You have described how you are working with three projects to implement 
>> your non-versioning scenario on Google Cloud Platform but I am unclear 
>> about your question. Can you tell me more about how you are validating the 
>> application and building to production so I may research?
>>
>>
>> On Wednesday, January 6, 2021 at 11:32:13 AM UTC-5 Alex wrote:
>>
>>> Hi all, 
>>>
>>> Would love to hear your views on this. I run a Python app on GAE. I have 
>>> quite a few packages in my requirements.txt file, and I made the choice to 
>>> not version them. Which I understand means the latest version of each 
>>> requirement at the time of the project build will be used. 
>>>
>>> • Is that a 

[google-appengine] Newbie question - How to deploy node.js with manual garbage collection in app engine?

[Andrew Marunchak]

I'm running manual garbage collection every 30 seconds via  global.gc(); 
and my app.yaml file contains:

*entrypoint: node --expose_gc server*

However, when deploying, I eventually see a startup error displaying:

*Updating service [default] (this may take several minutes)...failed.ERROR: 
(gcloud.app.deploy) Error Response: [9]Application startup error! Code: 
APP_CONTAINER_CRASHED  *

Any insight would be greatly appreciated :[

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1c49448d-4e0d-4d32-aacc-2bf278d279aan%40googlegroups.com.

Re: [google-appengine] Migrating Python 2 to 3: images

['Andrew Gorcester' via Google App Engine]

The migration guide does have a brief section in the overview:
https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/migrating-services
which
suggests migrating to third-party image services. However, depending on
your use case (keeping in mind impacts on security and performance) you may
find it more suitable to install a library which performs the operation
in-place on your App Engine instance. Pillow is one I have used in the past.

On Mon, Feb 24, 2020 at 12:18 PM Joshua Smith 
wrote:

> I need to read and resize an image in my google app engine app. In my
> python2.7 code, this is simply:
>
> from google.appengine.api import images
> image = images.resize(image, width=1024, output_encoding=images.JPEG,
> correct_orientation=images.CORRECT_ORIENTATION)
>
> I can’t find anything the migration guide that suggests an alternative to
> this API (but several places say I need to find one). So helpful.
>
> What does this august body recommend I use to replace the above two lines
> of code? I certainly don’t want to have to use some web-based micro-service
> for such a simple thing.
>
> -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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/DA44AE42-4D42-47C1-BE0B-9726516FF865%40gmail.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJtX7KbauQa9nFwpJzOHCDLTKRTG_eSRiz8bfGJ5sU7Pg%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

I'm afraid none of the Cloud API-targeting libraries have testbed support,
as testbed was a solution to App Engine Gen 1-specific problems at the
time. If you have an example of how much slower the datastore emulator is
vs. testbed for your use case, that would be very helpful in prioritizing
further work, either in speeding up the emulator or replicating the testbed
system for Cloud. I'd recommend filing a bug with your experiences at
https://github.com/googleapis/python-ndb/issues (though this would
eventually be tackled by the entire Cloud Client libraries team, rather
than just the NDB team).

On Mon, Feb 24, 2020 at 1:05 PM Remko Tronçon  wrote:

> On Monday, February 24, 2020 at 9:52:25 PM UTC+1, Andrew Gorcester wrote:
> > Cloud NDB is compatible with the Cloud Datastore Emulator; we recommend
> tests be done using that, the same way on Cloud NDB as they would be with
> the Cloud Datastore library.
>
> Using an external emulator is way too slow to use for unit tests, even if
> you are able to get all your code changed so you don’ have to tear down and
> clean start the emulator to avoid interference between tests. This is
> pretty disappointing, and means I (and I expect many others) will be forced
> to rewrite everything if your app isn’t in pure maintenance mode.
>
> Remko
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/9f3246de-d324-4e33-b2d9-86f00a642aa5%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJY3MAHgOkknEm8WLEFq5-eXQLZwL%3DZ4Dt5G-LU6%3DyicA%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

Cloud NDB is intended as a migration tool for App Engine NDB users who wish
to move to either newer versions of App Engine (App Engine Python 3) or to
other environments. Customers are welcome to use Cloud NDB however they
wish, including on totally new projects that aren't associated with GAE
NDB. However, Cloud NDB will not add support for any new features that
might be added to Cloud Datastore in the future, because that wouldn't
further the goal of aiding migration from GAE NDB; also the NDB concurrency
model was designed around GAE Python 2.7 limitations and might not be the
best model for greenfield projects with no history rooted in App Engine. We
recommend the use of the Cloud Datastore library for new projects when
possible.

On Mon, Feb 24, 2020 at 12:08 PM Philip  wrote:

> In this ticket <https://github.com/googleapis/python-ndb/issues/289> it
> was stated that Google does not recommend NDB for new projects. It is
> merely intended for upgrading from 2.7 to python 3 GAE. It this statement
> still true given the fact that it is now GA?
>
> Am Montag, 24. Februar 2020 20:02:36 UTC+1 schrieb Andrew Gorcester:
>>
>> Hello Pythonistas,
>>
>>
>> The Cloud NDB client library for Cloud Datastore and Cloud Firestore in
>> Datastore mode, previously introduced as a beta project in September 2019,
>> has been launched to GA with its 1.0 release.
>>
>>
>> Cloud NDB is an updated version of the App Engine NDB client library for
>> Datastore, adding support for Python 3 and targeting the Datastore API.
>> While it is intended for users migrating from App Engine Python 2.7 to App
>> Engine Python 3, it is fully portable and compatible with other Python
>> platforms. The library can be installed with `pip install google-cloud-ndb`
>> and the source code can be found on Github at
>> https://github.com/googleapis/python-ndb.
>>
>>
>> We also have a migration guide for NDB
>> <https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb>
>> at, as part of our broader GAE Python migration documentation
>> <https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3>.
>> We'll continue updating and adding to this documentation and library as
>> part of our migration support effort, so please also continue sending us
>> your feedback.
>>
>>
>> Thank you again for your continued support for App Engine and our Cloud
>> platform. I am looking forward to hearing feedback from the community on
>> this and upcoming efforts.
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/322768f1-6716-436c-b4da-e8d17ed4ad77%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/322768f1-6716-436c-b4da-e8d17ed4ad77%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLs3NzYfuVxa8vkvt8oQNWeSt_c%3Ds%2BGUcU4QL18gNz1Cw%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

Cloud NDB is compatible with the Cloud Datastore Emulator; we recommend
tests be done using that, the same way on Cloud NDB as they would be with
the Cloud Datastore library.

On Mon, Feb 24, 2020 at 11:59 AM Remko Tronçon  wrote:

>
> We also have a migration guide for NDB
>> 
>> at, as part of our broader GAE Python migration documentation
>> .
>> We'll continue updating and adding to this documentation and library as
>> part of our migration support effort, so please also continue sending us
>> your feedback.
>>
>
> The migration guide doesn't mention how NDB unit tests can be ported.
> AFAIK, the testbed that is currently available in NDB is not available for
> Cloud NDB.
> Is there anything provided for unit testing Cloud NDB code, or do you have
> to abstract out NDB (which sounds like a huge effort and would pretty much
> make Cloud NDB useless).
>
> thanks,
> Remko
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/307e34e9-60ed-4534-a330-1adbad15255a%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFK_%3D5ibcb6UML-8wDeog0rDQ_0j%2BnR_fuLaytw4QfMCQQ%40mail.gmail.com.

[google-appengine] Cloud NDB is now GA

['Andrew Gorcester' via Google App Engine]

Hello Pythonistas,


The Cloud NDB client library for Cloud Datastore and Cloud Firestore in
Datastore mode, previously introduced as a beta project in September 2019,
has been launched to GA with its 1.0 release.


Cloud NDB is an updated version of the App Engine NDB client library for
Datastore, adding support for Python 3 and targeting the Datastore API.
While it is intended for users migrating from App Engine Python 2.7 to App
Engine Python 3, it is fully portable and compatible with other Python
platforms. The library can be installed with `pip install google-cloud-ndb`
and the source code can be found on Github at
https://github.com/googleapis/python-ndb.


We also have a migration guide for NDB

at, as part of our broader GAE Python migration documentation
.
We'll continue updating and adding to this documentation and library as
part of our migration support effort, so please also continue sending us
your feedback.


Thank you again for your continued support for App Engine and our Cloud
platform. I am looking forward to hearing feedback from the community on
this and upcoming efforts.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLfFqve1kvcUustO%3DjdsS%2ByLO-eOW1bOsQ2kqb3Yk2CnA%40mail.gmail.com.

Re: [google-appengine] Trouble to deploy and download dependencies

['Andrew Gorcester' via Google App Engine]

That message from pycrypto is misleading. xcode is only needed on osx. For
Windows you need a different way to install a C compiler. If you are using
Cygwin, there should be a Cygwin package for a compiler such as gcc
available but I'm afraid I am not certain about the details.

On Thu, Feb 13, 2020, 6:18 AM Dongcheng Li  wrote:

> Thank you. It passed this step. However, another issue appear
>
> Windows is now supported as of version 1.11. In the scripts directory,
> there are two batch files:
>
>- windows_start_local.bat starts a local dev server so you can explore
>Course Builder in your browser for testing.
>- windows_deploy.bat deploys your application to Google App Engine.
>
> Note: If you have an older version of Windows, you may need to manually
> download Cygwin <https://www.cygwin.com/>. Watch the terminal for errors
> and instructions.
>
> When I run  windows_start_local.bat   OR  windows_deploy.bat,  the window
> of Command Prompt showed
> [image: image.png]
>
> I am wondering how I can run $ xcode-select --install from Command Prompt.
>
> Thank you for your help.
>
> DC
>
>
>
>
> On Wed, Feb 12, 2020 at 5:17 PM 'Andrew Gorcester' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> Hi, you're probably looking at the Course Builder documentation on a
>> windows machine, right? You can install Cygwin, or if you have Windows 10,
>> you can instead install Windows Subsystem for Linux, and that should get
>> you a command prompt from which you can run bash without issue.
>>
>> On Wed, Feb 12, 2020, 1:45 PM Dongcheng Li  wrote:
>>
>>>
>>> Before you deploy, ensure you have all the things (like libraries, other
>>> software) you need to be successful. The deploy script mentioned in the
>>> section below will try to download any dependencies also, but in this step
>>> you will get more messages about the process. These messages may help you
>>> if anything is wrong. To download dependencies, open a command prompt and
>>> get to your coursebuilder directory. Type the following command:
>>>
>>> bash ./scripts/common.sh
>>>
>>>
>>> I am stuck on this step. After type this command, it showed
>>>
>>> [image: 1581542250(1).png]
>>>
>>> Does anyone know what caused it? Any clue? Thanks.
>>>
>>> DC
>>>
>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/a9745897-36db-4ca8-a434-7cc9dd747a9c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-appengine/a9745897-36db-4ca8-a434-7cc9dd747a9c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BCZKCS72VJ5-WMGN%3DQn1XNfTmm8KRc%2BDFp1XJaz8eTHA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BCZKCS72VJ5-WMGN%3DQn1XNfTmm8KRc%2BDFp1XJaz8eTHA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CALkCzHZM%3DpsOuSQuwRLYMcipy%3D_FDkoPirKS-DZujrph-Yae%3DA%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-appengine/CALkCzHZM%3DpsOuSQuwRLYMcipy%3D_FDkoPirKS-DZujrph-Yae%3DA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2Bh6P9eL2ouRXxfQ65-13X_JGZVFgYy0rqmAoaMVvZqFQ%40mail.gmail.com.

Re: [google-appengine] Trouble to deploy and download dependencies

['Andrew Gorcester' via Google App Engine]

Hi, you're probably looking at the Course Builder documentation on a
windows machine, right? You can install Cygwin, or if you have Windows 10,
you can instead install Windows Subsystem for Linux, and that should get
you a command prompt from which you can run bash without issue.

On Wed, Feb 12, 2020, 1:45 PM Dongcheng Li  wrote:

>
> Before you deploy, ensure you have all the things (like libraries, other
> software) you need to be successful. The deploy script mentioned in the
> section below will try to download any dependencies also, but in this step
> you will get more messages about the process. These messages may help you
> if anything is wrong. To download dependencies, open a command prompt and
> get to your coursebuilder directory. Type the following command:
>
> bash ./scripts/common.sh
>
>
> I am stuck on this step. After type this command, it showed
>
> [image: 1581542250(1).png]
>
> Does anyone know what caused it? Any clue? Thanks.
>
> DC
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/a9745897-36db-4ca8-a434-7cc9dd747a9c%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BCZKCS72VJ5-WMGN%3DQn1XNfTmm8KRc%2BDFp1XJaz8eTHA%40mail.gmail.com.

Re: [google-appengine] Pull Queue Deprecation?

['Andrew Gorcester' via Google App Engine]

App Engine Tasks (available for App Engine Standard Gen 1 runtimes) will
continue to support both push and pull, but Cloud Tasks (available for all
products) will not support pull queues. Instead, we recommend Cloud Pub/Sub
for this use case. Please see this documentation for details:
https://cloud.google.com/appengine/docs/standard/java/taskqueue/pull/migrating-pull-queues

Please let us know if Cloud Pub/Sub doesn't solve your needs in this area,
so we can improve our decisions for future features.

On Fri, Jan 10, 2020 at 11:10 AM Jim  wrote:

> I have an app running on Google App Engine Standard using the Java 8
> runtime, and it uses both push and pull queues extensively.  When I'm using
> the Google Cloud Platform management console I interact with my Push and
> Pull Queues under the "Cloud Tasks" UI option, but all of my code
> interaction with queues is via the com.google.appengine.api.taskqueue Java
> package.  Lately I'm seeing notices about Google Cloud Tasks Pull Queues
> being deprecated.  Can someone in the GAE team please clarify for me, will
> my usage of Pull Queues be supported going forward?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/588d3ad9-03f8-47c1-afa2-f2b4d993caae%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFK3YMkOrsVYjcJJzX06gic4-eHJZ79j8d_RmpRtHsrawQ%40mail.gmail.com.

Re: [google-appengine] Re: App Engine, MySQL and private ip

['Andrew Gorcester' via Google App Engine]

Hi Charlotte,

Additionally, once you have a private Cloud SQL IP address, I think you
should be able to connect to it from App Engine by using Serverless Virtual
Private Cloud Access:
https://cloud.google.com/vpc/docs/configure-serverless-vpc-access .

On Wed, Dec 4, 2019 at 3:32 PM 'Elliott (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Charlotte,
>
> You can get a private IP when you create a Cloud SQL instance under
> “Configuration Options”. I hope this helps.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/58f84428-a784-4f58-8aea-c739eaad316b%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2B9kXcMbWfWrJLX_rPDoAnBXidDoH_rD5j%3D0P-koxbwew%40mail.gmail.com.

Re: [google-appengine] Python 3.7 and Python 2 ndb cache conflict

['Andrew Gorcester' via Google App Engine]

Hi Eliran,

On Python 3, you can use Cloud Memorystore to provide a Redis cache.
However, you can't currently share a cache between the Python 2.7 and
Python 3.7 versions of the GAE. The cache will be separate, which will be
an issue as you describe if you are running both Python 2 and Python 3
versions targeting the same Datastore database.

Now that Cloud NDB supports Python 2.7 in addition to Python 3.7, you could
try to solve this problem by replacing your GAE NDB with Cloud NDB on
Python 2.7, and then pointing it at the same Redis instance as the Python
3.7 version. Instead of sharing Memcache, you can share Redis. See the
documentation for more info:
https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb

On Wed, Dec 4, 2019 at 5:20 AM 'Eliran Segev' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hi, we are migrating our python 2 services to python 3.
>
>
> In python 2 we are using NDB - that uses Memcache
> In python 3 we are using cloud NDB - that cannot have Memcache as cache
> provider
>
> And now we have a problem when updating an entity from Python 3 it does
> not affect the cache, and when using Python 2 we get the cached copy of
> this entity.
>
>
> Without changing python 2 code to cloud NDB, how can we solve this and
> still have cache?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/19ecce3c-e774-491f-a168-40b99393c651%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLerNxFOi7-6T_9aNpJzD0KqDmoimNAJ%2Bm3PSmxTmi3uQ%40mail.gmail.com.

Re: [google-appengine] Re: GAE Standard | Local Dev | Python37: google.appengine.api not found

['Andrew Gorcester' via Google App Engine]

Unfortunately there is not currently any Google Cloud replacement for the
GAE Mail API. We are aware of the gap in our migration story and are
working to fix it.

On Mon, Nov 25, 2019, 5:44 PM Yanay Lehavi  wrote:

> Thank you Andrew. We have migrated most of our stuff to py37 and
> everything works very well so far. I'm familiar with the documentation. The
> reason I started this thread is I'm trying to migrate automated email
> (which in 27 call the appengine.api package). It looks like there's no way
> to send email under 37?
>
> Thanks!
>
> On Monday, November 25, 2019 at 12:00:22 PM UTC-8, Andrew Gorcester wrote:
>>
>> Hi Yanay,
>>
>> I'm an engineer at Google working on making the migration from GAE Python
>> 2.7 (a Gen 1 runtime) to Python 3.7 (a Gen 2 runtime) clearer for users. In
>> addition to the page Ryan linked above which explains the differences, we
>> have also recently published this migration homepage with some tutorials
>> and examples:
>> https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/
>>
>> Please take a look and let us know if you need more specific information.
>> Thanks!
>>
>> On Mon, Nov 25, 2019 at 9:58 AM Ryan B  wrote:
>>
>>> hi Yanay! the classic App Engine APIs in google.appengine.api aren't 
>>> available
>>> in the Python 3 runtime. More details:
>>> https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis
>>>
>>>
>>> On Sunday, November 24, 2019 at 6:08:57 PM UTC-8, Yanay Lehavi wrote:
>>>>
>>>> I see a number of threads on this in git etc. but they all seem
>>>> unresolved:
>>>>
>>>> >>> import google.appengine.api
>>>>
>>>> Traceback (most recent call last):
>>>>
>>>>   File "", line 1, in 
>>>>
>>>> ModuleNotFoundError: No module named 'google'
>>>>
>>>> >>>
>>>>
>>>> In the above mentioned threads, some people suggested various env vars,
>>>> none of which I have, nor ever needed... (been developing GAE locally for a
>>>> long time).
>>>> My platform: Mac Catalina.
>>>> Anyone knows how to resolve this?
>>>> Many thanks
>>>>
>>> --
>>> 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-a...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/2fbbae44-76e6-4e28-9cc6-3c4bfe50f074%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-appengine/2fbbae44-76e6-4e28-9cc6-3c4bfe50f074%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/5ee38ced-fcd4-4f8f-bf80-2e1b4b51338f%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/5ee38ced-fcd4-4f8f-bf80-2e1b4b51338f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJd8BMzetwv3omnF4XnQZ639-vtsBqF0f_TJ_f0%3DU9PcQ%40mail.gmail.com.

Re: [google-appengine] Re: GAE Standard | Local Dev | Python37: google.appengine.api not found

['Andrew Gorcester' via Google App Engine]

Hi Yanay,

I'm an engineer at Google working on making the migration from GAE Python
2.7 (a Gen 1 runtime) to Python 3.7 (a Gen 2 runtime) clearer for users. In
addition to the page Ryan linked above which explains the differences, we
have also recently published this migration homepage with some tutorials
and examples:
https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/

Please take a look and let us know if you need more specific information.
Thanks!

On Mon, Nov 25, 2019 at 9:58 AM Ryan B  wrote:

> hi Yanay! the classic App Engine APIs in google.appengine.api aren't available
> in the Python 3 runtime. More details:
> https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis
>
>
> On Sunday, November 24, 2019 at 6:08:57 PM UTC-8, Yanay Lehavi wrote:
>>
>> I see a number of threads on this in git etc. but they all seem
>> unresolved:
>>
>> >>> import google.appengine.api
>>
>> Traceback (most recent call last):
>>
>>   File "", line 1, in 
>>
>> ModuleNotFoundError: No module named 'google'
>>
>> >>>
>>
>> In the above mentioned threads, some people suggested various env vars,
>> none of which I have, nor ever needed... (been developing GAE locally for a
>> long time).
>> My platform: Mac Catalina.
>> Anyone knows how to resolve this?
>> Many thanks
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/2fbbae44-76e6-4e28-9cc6-3c4bfe50f074%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLu%3D2S%2B_w_et%2B35QOaM_w7R6J-JiB%2BDcoVMXcy7s1S%3DNg%40mail.gmail.com.

Re: [google-appengine] Django Channels Support in Google App Engine

['Andrew Gorcester' via Google App Engine]

Websockets are supported on Google App Engine Flexible Environment. They
are not supported on Standard Environment at this time.

On Tue, Nov 19, 2019, 6:50 PM Ranjan Barat  wrote:

> Hello All, Please help us in understanding if we have support for Django
> Channels & WebSockets support in Google App Engine, if not, then whats best
> available solution
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/6bdeb497-0273-4da8-bfc2-fcb578d48798%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJwXKmR8xPJez31-%3DMXrURrQ9oaOzH9AFCNx6o7-9Yr9A%40mail.gmail.com.

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

['Andrew Gorcester' via Google App Engine]

That does make sense. If you could bridge the gap by using a single static
file directory in app.yaml served with a single static_dir handler, that
might work too. But I know some apps have very complex app.yaml defined
static files, so I understand why you're looking at the dev_appserver.py
option instead.

On Fri, Nov 8, 2019 at 3:33 PM Ryan Barrett  wrote:

> thanks for the reply!
>
> On Fri, Nov 8, 2019 at 2:40 PM 'Andrew Gorcester' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> I would recommend trying to solve the first problem and serving static
>> files locally.
>>
>
> understood, but using a different static file server is not great. it
> makes local development diverge significantly from production. local no
> longer uses or tests app.yaml's static file handlers, but prod does, so
> bugs will eventually pop up that only happen in production, and are thus
> harder to test for and debug.
>
> for that reason, i'm actually going the other way and using dev_appserver
> right now, soi still have some confidence that my app will behave more or
> less the same in production that it does locally. the minute long delay on
> startup is definitely painful though.
>
>
> At first glance I think the most straightforward ways to do that would be
>> to either:
>>
>> - Use the Flask development server instead of gunicorn and leverage
>> Flask's integrated /static directory
>> https://flask.palletsprojects.com/en/1.1.x/tutorial/static/
>> - If you prefer to use gunicorn or you need more serving options, add
>> WhiteNoise middleware to your app; ideally, have your app detect whether
>> it's running in production or in development mode and conditionally add
>> WhiteNoise in development only: http://whitenoise.evans.io/en/stable/
>>
>>
>> On Fri, Nov 8, 2019 at 2:21 PM Ryan B  wrote:
>>
>>> Hi all! My Python 3 topic for the day is local development. How are you
>>> all doing it? Any tips?
>>>
>>> The two main ways seem to be a third party server, eg Flask or Gunicorn,
>>> or dev_appserver.py. I have both working, but each one has a fatal flaw
>>> that makes it basically unusable for me so far.
>>>
>>> When I run my app with eg gunicorn -b :8080 app:application - the way
>>> Google recommends
>>> <https://cloud.google.com/appengine/docs/standard/python3/testing-and-deploying-your-app#running_locally>
>>> - it works, but doesn't serve any assets from static file handlers in my
>>> app.yaml. This is widely reported on StackOverflow
>>> <https://stackoverflow.com/search?q=%5Bgoogle-app-engine%5D+%5Bpython-3.x%5D+static>
>>> and elsewhere. Responses are often some variation of, "why do you need
>>> static assets for dynamic requests?" The obvious reason is that pretty much
>>> all webapps use images, CSS, and/or JS, among other static files. They're
>>> generally not usable without those assets.
>>>
>>> When I run my app with  dev_appserver.py, it creates a new virtualenv
>>> and installs all of my dependencies from requirements.txt. This is
>>> nice, but also extremely slow for any nontrivial app. My current medium
>>> sized app has 155 packages, and even when they're all cached locally,
>>> installing them takes around 60s. I often switch between different apps and
>>> other stacks, so I can't often keep dev_appserver running for hours or days
>>> on end to avoid this. (I've filed this feature request for
>>> dev_appserver to reuse an existing virtualenv.
>>> <https://issuetracker.google.com/u/1/issues/144150446>)
>>>
>>> Let me know if you have any ideas!
>>>
>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> 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/BJDE8y2KISM/unsubscribe
>> .
>> To unsubscribe from this group

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

['Andrew Gorcester' via Google App Engine]

Hi Ryan,

I would recommend trying to solve the first problem and serving static
files locally.

At first glance I think the most straightforward ways to do that would be
to either:

- Use the Flask development server instead of gunicorn and leverage Flask's
integrated /static directory
https://flask.palletsprojects.com/en/1.1.x/tutorial/static/
- If you prefer to use gunicorn or you need more serving options, add
WhiteNoise middleware to your app; ideally, have your app detect whether
it's running in production or in development mode and conditionally add
WhiteNoise in development only: http://whitenoise.evans.io/en/stable/


On Fri, Nov 8, 2019 at 2:21 PM Ryan B  wrote:

> Hi all! My Python 3 topic for the day is local development. How are you
> all doing it? Any tips?
>
> The two main ways seem to be a third party server, eg Flask or Gunicorn,
> or dev_appserver.py. I have both working, but each one has a fatal flaw
> that makes it basically unusable for me so far.
>
> When I run my app with eg gunicorn -b :8080 app:application - the way
> Google recommends
> 
> - it works, but doesn't serve any assets from static file handlers in my
> app.yaml. This is widely reported on StackOverflow
> 
> and elsewhere. Responses are often some variation of, "why do you need
> static assets for dynamic requests?" The obvious reason is that pretty much
> all webapps use images, CSS, and/or JS, among other static files. They're
> generally not usable without those assets.
>
> When I run my app with  dev_appserver.py, it creates a new virtualenv and
> installs all of my dependencies from requirements.txt. This is nice, but
> also extremely slow for any nontrivial app. My current medium sized app has
> 155 packages, and even when they're all cached locally, installing them
> takes around 60s. I often switch between different apps and other stacks,
> so I can't often keep dev_appserver running for hours or days on end to
> avoid this. (I've filed this feature request for dev_appserver to reuse
> an existing virtualenv.
> )
>
> Let me know if you have any ideas!
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BPRh3vU%3Dpp3708sRAFE8%2BYxC%3Dm%2BmC8oGVqHyLw3yKBhw%40mail.gmail.com.

Re: [google-appengine] Re: Cloud NDB Datastore library Beta

['Andrew Gorcester' via Google App Engine]

After consulting with product management, I can clarify that Cloud NDB will
be treated the same as other Cloud Client libraries on github and so is not
covered explicitly by our Cloud Support contract, though I'm not personally
familiar with our support contract language so I can't go into any greater
detail.

On Thu, Sep 26, 2019 at 8:05 PM 'Mario Jimenez Leon' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> This is great news!
>
>
>
> The library is gonna be supported by GCP support until the beta phase
> ends. You can track the changes in the changelog of the library in github:
> https://github.com/googleapis/python-ndb/blob/master/CHANGELOG.md
>
>
>
> Currently, we don't have an Estimated Time of Arrival for the new version.
>
>
> On Thursday, September 26, 2019 at 1:01:48 AM UTC-5, Soeren Balko wrote:
>>
>> Great news and good to see Google (finally!) reacting to the Python 2 EOL
>> dilemma and its repercussions on AppEngine!
>>
>> A couple of question though:
>>
>> (1) "beta" is not very reassuring in a sense that we have millions of
>> users in our AppEngine/DataStore backend. When will the library come out of
>> beta?
>> (2) Does the library come under Google Cloud support contracts?
>>
>> Thank you,
>> Soeren
>>
>>
>> On Friday, September 20, 2019 at 7:33:38 AM UTC+10, Andrew Gorcester
>> wrote:
>>>
>>> Hello Pythonistas,
>>>
>>> I'm pleased to announce the Beta release of Cloud NDB, an updated
>>> version of the App Engine NDB client library for Datastore to support the
>>> GAE Python 3 runtime and other Python platforms. Our goal with Cloud NDB
>>> and related efforts is to ensure App Engine Python 2.7 applications are
>>> fully portable and can smoothly migrate to Python 3.
>>>
>>> The library can be installed with `pip install google-cloud-ndb` and the
>>> source code can be found at https://github.com/googleapis/python-ndb.
>>> Please refer to our newly published migration guide at
>>> https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb,
>>> and our API documentation at
>>> https://googleapis.dev/python/python-ndb/latest/index.html.
>>>
>>> We're grateful to have received generous user support in testing,
>>> comments, bug reports and even code contributions in our Alpha phase, and
>>> we hope the community will continue to send feedback as we work towards GA.
>>> Please see our GitHub repository linked above to follow development and
>>> communicate with our team, or email me directly at gorc...@google.com.
>>>
>>> While Cloud NDB can be used freely by any Cloud Datastore (and Firestore
>>> in Datastore mode) customers, it is intended to facilitate migration to
>>> Python 3 for App Engine NDB users; our recommendation for new apps is still
>>> to use the Cloud Client Datastore or Firestore libraries which are part of
>>> the Google Cloud SDK.
>>>
>>> Thanks for your continued support of our platform. I am looking forward
>>> to hearing from the community on this and upcoming efforts.
>>>
>>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/83877d90-87e6-46ea-8b9a-39b3e68e1c16%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/83877d90-87e6-46ea-8b9a-39b3e68e1c16%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFKOs7Qa8g0Eac3Y9qoFO2m-f8k1SPMwPS-i%3DkWnz5ACfQ%40mail.gmail.com.

[google-appengine] Cloud NDB Datastore library Beta

['Andrew Gorcester' via Google App Engine]

Hello Pythonistas,

I'm pleased to announce the Beta release of Cloud NDB, an updated version
of the App Engine NDB client library for Datastore to support the GAE
Python 3 runtime and other Python platforms. Our goal with Cloud NDB and
related efforts is to ensure App Engine Python 2.7 applications are fully
portable and can smoothly migrate to Python 3.

The library can be installed with `pip install google-cloud-ndb` and the
source code can be found at https://github.com/googleapis/python-ndb.
Please refer to our newly published migration guide at
https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb,
and our API documentation at
https://googleapis.dev/python/python-ndb/latest/index.html.

We're grateful to have received generous user support in testing, comments,
bug reports and even code contributions in our Alpha phase, and we hope the
community will continue to send feedback as we work towards GA. Please see
our GitHub repository linked above to follow development and communicate
with our team, or email me directly at gorces...@google.com.

While Cloud NDB can be used freely by any Cloud Datastore (and Firestore in
Datastore mode) customers, it is intended to facilitate migration to Python
3 for App Engine NDB users; our recommendation for new apps is still to use
the Cloud Client Datastore or Firestore libraries which are part of the
Google Cloud SDK.

Thanks for your continued support of our platform. I am looking forward to
hearing from the community on this and upcoming efforts.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFK8O7YH2gaDCSUQ7vVeM2%3DWoTR%3DXBAz%3DgkFZmbt4oatQQ%40mail.gmail.com.

Re: [google-appengine] Re: Brazil IP

['Andrew Gorcester' via Google App Engine]

Hi Manu,

My observation in the past is that IP geolocation from third party services
is generally not accurate for cloud servers. The server and egress points
are still located in South America as advertised and will have low latency
to South American clients. Unfortunately there is no reliable way that I
know of to control what third party geolocation services report as the
estimated location of the IP address.


On Wed, Aug 28, 2019, 2:16 AM Manu Campos  wrote:

> Hi,
> My VM zone is southamerica-east1-b, but the external IP I received is
> 35.199.93.41 which is located in California.
> I need an IP from Brazil.
> Can you help me?
>
>
> 
>  Livre
> de vírus. www.avast.com
> .
> <#m_2297655411792827469_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> Em ter, 27 de ago de 2019 às 13:38, 'George (Cloud Platform Support)' via
> Google App Engine  escreveu:
>
>> Hello Manu,
>>
>> To get an IP from Brazil, you have the option to choose region
>> southamerica-east1 a, b, c Osasco (São Paulo), Brazil, from the Regions and
>> Zones list .
>> Practical details are to be found on the "Reserving a Static External IP
>> Address" documentation page
>> .
>> It may be worthwhile reading related information on the "Best practices for
>> Compute Engine regions selection" page
>> 
>> .
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-appengine/ac7c35d7-bf87-4759-a3c7-0423bfa232e8%40googlegroups.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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CACSgnbOWE-6wXiHW8udyS-2kAggrKy3GPtKzhDXkXjNi2GUkcQ%40mail.gmail.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLazdAwkxdSF82UeGzCd_-HyzVhmHy3kH_e_P7wp6ef2A%40mail.gmail.com.

Re: [google-appengine] Re: Source Code download from GAE Flex

['Andrew Gorcester' via Google App Engine]

As a workaround, may I suggest enabling debug mode and SSHing into a
running instance to inspect the filesystem directly? You might be able to
exfiltrate the code manually.
https://cloud.google.com/appengine/docs/flexible/python/debugging-an-instance

On Tue, Aug 20, 2019 at 10:16 AM 'Nicolas (Google Cloud Platform Support)'
via Google App Engine  wrote:

> Hi Sai,
>
> It used to be possible to download your source code with the appcfg.py
> tools but unfortunately this tool is now deprecated and it’s replacement,
> the Cloud SDK   does not support this
> feature.
> There is a feature request for this, and you can follow their progress
> here , although there is no
> ETA for when it will be implemented.
>
> On Monday, August 19, 2019 at 6:26:58 PM UTC-4, Sai M wrote:
>>
>> Hello,
>>
>> By accident i have lost the data on my personal laptop where i have kept
>> the Source code of the project i have deployed on Google App Flex.
>> Unfortunately i don't have the backup as it happened by accident when i was
>> trying to upgrade my OS.
>>
>> The Project ID is..."smartcc".
>>
>> Can you pls. help on instructions of how to down load the latest
>> application source code deployed on Google App Flex env please.
>>
>> Thanks a ton in advance.
>>
>> Best Regards
>> Sai
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/e52822af-78fd-45dc-97d1-4a72915fe6ef%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFKkbxfDY6kXoXB_-E8n8HB_C_o1LM217PbYRXmTEoVhDg%40mail.gmail.com.

Re: [google-appengine] Re: Install Redis Slave on App Engine Flex

['Andrew Gorcester' via Google App Engine]

May I suggest using a custom runtime? You should be able to install and
configure Redis using the Dockerfile system.
https://cloud.google.com/appengine/docs/flexible/custom-runtimes/

On Fri, Jul 26, 2019 at 12:05 PM 'Biswajit Mukhopadhyay' via Google App
Engine  wrote:

> I want a read replica (Redis Slave) to be installed in all App Engine Flex
> instance. Reading from local will increase the performance of the app than
> reading from Memory Store Redis (Reading operation of our app is much
> higher than writing operation). Memory Store Redis will be used as a Master
> and write operation will happen on that Master.
>
>
> On Friday, July 26, 2019 at 8:39:01 PM UTC+5:30, Julie (cloud platform
> support) wrote:
>>
>> You can connect Memorystore for redis with App Engine Flex using this
>> example
>> and
>> if you would like high availability
>>  for
>> Memorystore it is available for Redis instances with the Standard
>> Tier configuration. To clarify, do you want the Redis replica to be
>> connected to it's App Engine Flex instance or Memorystore for Redis as if
>> you are interested in the latter, high availability
>> 
>> cannot be used as a read replica.
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/212ed959-6549-4abc-87f1-ebcf3c2a3ea4%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2BmUZNW_b0SG4eKtV56jt2oTzmOtafdn6XnhucukYZ9SQ%40mail.gmail.com.

Re: [google-appengine] Re: No Pull Queues for Node.js Standard Environment?

['Andrew Gorcester' via Google App Engine]

Pardon my interjection, my team works on these docs and so I might be able
to comment up front. The Python 2.7 (only) and Go 1.9 (only) runtimes are
"first generation" App Engine runtimes which use the App Engine Task Queues
API which is internal to App Engine and not compatible with other products.
The other runtimes, including the newer versions of Python and Go and also
other supported languages such as Node, are "second generation" App Engine
runtimes and instead of using App Engine-specific APIs, they have access to
the Cloud-wide APIs such as Cloud Tasks and Cloud Pub/Sub which are what we
recommend going forward.

In the specific case of pull queues, we instead recommend using the Cloud
Pub/Sub API which provides much of the pull queue functionality separate
from Task Queues. However, if this doesn't serve your needs, please reply
to this email (or directly to me) with feedback as we're actively gathering
customer feedback about any use cases that aren't covered by the new APIs.



On Mon, Jul 15, 2019 at 1:17 PM 'Elliott (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Govind,
>
> To have your question addressed, please click the “Send Feedback” link at
> the bottom of this page
> ,
> then “Documentation feedback” and follow the steps to ask your question.
> The documentation team will look into this matter for you.
>
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/031d9fff-3d72-47be-9152-80c225e0f92f%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJc%2Br%2Bpd_4t%3D2U-m1jWqXNgQyDZs0m0ybHPfmVH5yvHYA%40mail.gmail.com.

[google-appengine] Re: Permission denied when deploying queue.yaml

[Andrew Buck]

Thanks, I filed an issue tracker: 
https://issuetracker.google.com/issues/137078982

On Tuesday, July 9, 2019 at 8:26:38 AM UTC-7, Julie (cloud platform 
support) wrote:
>
> It seems from this document 
>  that what 
> you have granted permissions for Cloud Tasks for should be sufficient as 
> cloudtasks.queues.update is needed to modify an existing task. 
>
> It does seem that that appengineDeployQueue is App Engine-specific Gradle 
> task  
> which
>  
> likely means it requires App Engine roles 
>  and 
> perhaps additional actions to use Gradle plugin 
>  if 
> you have not done so yet. 
>
> This will likely require investigation into your permissions so I suggest 
> opening an issue tracker 
>  
> if the above suggestions do not resolve the issue. Please note I provided 
> all documents in App Engine Standard format but Flex documents should 
> exist. 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5e42ccb3-e566-45cd-809e-98b4cc03ebab%40googlegroups.com.

[google-appengine] Permission denied when deploying queue.yaml

[Andrew Buck]

When I attempt to use a service account to deploy an updated queue.yaml, I 
get the following error:

*ERROR: (gcloud.app.deploy) PERMISSION_DENIED: The caller does not have 
permission*
*> Task :appengineDeployQueue FAILED*

What permissions does the service account need for this operation? I 
already gave it both Cloud Tasks Admin and Cloud Tasks Queue Admin and it 
still get the error.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/89755f7c-44fc-411a-8b25-12ca1d394155%40googlegroups.com.

[google-appengine] Re: Will App Engine Flex Environment ever support Memcache?

[Andrew Buck]

It's been almost a year. Is support for Memcache on App Engine Flex still 
planned?

On Tuesday, August 7, 2018 at 11:03:49 AM UTC-7, Gopal Ashok wrote:
>
> Hi Joshua,
> App Engine Memcache for Flex alpha is closed. 
>
> The current caching story for App Engine Flex is Cloud Memorystore (Beta) 
> which currently supports Redis. We do plan to provide support for Memcache 
> that can be accessed from Flex. We will have a closed alpha for this in 
> late Q3\early Q4 timeframe. 
>
> If you need a managed memcache service one option is to use redislabs.
>
> https://cloud.google.com/appengine/docs/flexible/python/using-redislabs-memcache
>
> Thanks
> Gopal
>
>
> On Tuesday, July 24, 2018 at 3:29:40 PM UTC-7, Joshua Lyon wrote:
>>
>> Thanks for the reply. I signed up for both Memcache (Flex) and Could 
>> Tasks alpha access several days/weeks ago and never heard anything back... 
>> hence the reason I'm posting here to get clarification.
>>
>> It's unclear if some of these alphas are just not actually open yet, if 
>> they aren't accepting new requests, if the request just got lost, or what's 
>> going on. As such, I was hoping to get some clarification! :-D
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4c56bd97-a197-4024-b943-9a9eb686cd8b%40googlegroups.com.

Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

['Andrew Gorcester' via Google App Engine]

We don't have a replacement for that functionality yet, but I'll record
that that's a missing link for people migrating. Thank you!

On Fri, Jun 14, 2019 at 3:02 PM Nicolas Grilly 
wrote:

> On Friday, June 14, 2019 at 11:10:21 PM UTC+2, Andrew Gorcester wrote:
>>
>> If you don't mind me asking, what are the features of dev_appserver.py
>> that are still useful with the newer runtimes, which do not have App
>> Engine-specific APIs and client libraries that dev_appserver was originally
>> intended to mock and emulate?
>>
>
> dev_appserver.py seems still useful to emulate dispatch.yaml and static
> handlers locally. Is there an alternative?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJvgea0PLXyRvcXP%3DDg-Lhoo2VDUXiVfNKT%2BYMxR%2BBCBg%40mail.gmail.com.

Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

['Andrew Gorcester' via Google App Engine]

The recommended alternative is to use what is idiomatic for your framework
or other development process, as you would outside of Google Cloud. This is
now possible because we no longer require the use of App Engine-specific
APIs, handlers definitions, etc. However, dev_appserver.py did have some
features beyond emulating App Engine APIs and processing handlers that some
people have integrated into their workflows, so if this new approach
doesn't work well for you, please let us know where the pain points are.

On Fri, Jun 14, 2019 at 2:10 PM James Crowley 
wrote:

> If there are alternatives I'm missing this would be awesome? The feedback
> cycle is super slow when testing Google cloud specific code when it takes
> 30 seconds+ to update a running app (and that's ignoring the downsides of
> only being able to work online)
>
> Thanks
>
> J
>
> On Friday, 14 June 2019 01:32:52 UTC+2, James Crowley wrote:
>>
>>
>> Am I right in inferring that dev_appserver.py is on the way to being
>> deprecated, given the later language versions are not supported?
>>
>> I've tripped up trying to use it in the php7 environment - it prompts me
>> to provide a --php_executable argument for php72 environments (making me
>> think it was supported), but then doesn't seem to actually support the
>> environment ("The url "/" does not match any handlers." which goes away
>> when you use the php55 app.yaml syntax for specifying handlers rather than
>> the single entrypoint parameter)
>>
>> I then noticed it's not mentioned in the docs for php72/Java 11 etc at
>> all?
>>
>> Thanks!
>>
>> James
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/23ab05d6-eb3b-45f2-8282-479f7c3f14ec%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLGEJAHFMnAAvcfkTNYfRQVa6DnqKCEb50R1PTxbuDKGA%40mail.gmail.com.

Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

['Andrew Gorcester' via Google App Engine]

We're aiming to build all of our new runtimes so that they don't require
dev_appserver.py, by making them support the same APIs and idiomatic local
development practices that one would use on any platform. If you don't mind
me asking, what are the features of dev_appserver.py that are still useful
with the newer runtimes, which do not have App Engine-specific APIs and
client libraries that dev_appserver was originally intended to mock and
emulate?

On Fri, Jun 14, 2019 at 9:31 AM 'Nicolas (Google Cloud Platform Support)'
via Google App Engine  wrote:

> Hi James,
>
>
>
> Thanks for opening this thread,
>
>
>
> To answer your question you are right the dev_appserver.py
> 
> is not supported with the PHP 7.2 and PHP 7.3 runtimes.
>
>
>
> To test your app locally you can download and install PHP 7.2 or PHP 7.3
> and set up a web server.
>
>
> Dev_appserver.py will still be available for PHP 5/7
> 
> and no deprecation is planned for the moment.
>
>
>
>
>
> On Thursday, June 13, 2019 at 7:32:52 PM UTC-4, James Crowley wrote:
>>
>>
>> Am I right in inferring that dev_appserver.py is on the way to being
>> deprecated, given the later language versions are not supported?
>>
>> I've tripped up trying to use it in the php7 environment - it prompts me
>> to provide a --php_executable argument for php72 environments (making me
>> think it was supported), but then doesn't seem to actually support the
>> environment ("The url "/" does not match any handlers." which goes away
>> when you use the php55 app.yaml syntax for specifying handlers rather than
>> the single entrypoint parameter)
>>
>> I then noticed it's not mentioned in the docs for php72/Java 11 etc at
>> all?
>>
>> Thanks!
>>
>> James
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/478d514d-d1b4-46a4-9e91-9fb715cc7439%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJkJkRJJRqpMeCjB4LSY50oYS4TnB67TLqAgf6cbLQ9Ww%40mail.gmail.com.

[google-appengine] Python 3 NDB Datastore library alpha

['Andrew Gorcester' via Google App Engine]

Hello Pythonistas,

As part of our efforts to ensure App Engine Standard Python 2.7 users are
able to migrate to Python 3, we are developing an updated version of the
NDB Datastore client library that is compatible with Cloud Datastore and
Python 3.

I'm pleased to announce the new Python 3 NDB is in Alpha and is ready for
initial user testing. I'd appreciate it if anyone interested in migrating
NDB-using GAE Python 2.7 apps could take our new version for a spin and
send in their comments. The primary target platform is the GAE Python 3
runtime, but unlike the original version of NDB, this library does not rely
on App Engine specifics and should run anywhere.

The library can be installed with `pip install google-cloud-ndb` and the
source code can be found here: https://github.com/googleapis/python-ndb.
Please refer to MIGRATION_NOTES.md (
https://github.com/googleapis/python-ndb/blob/master/MIGRATION_NOTES.md)
for usage details; in particular, read the "Bootstrapping" section.

API documentation is published here:
https://googleapis.github.io/python-ndb/latest/ and the original
documentation for the Python 2.7 version is still available here:
https://cloud.google.com/appengine/docs/standard/python/ndb/ with more
detailed usage information, though not all of it will apply to the new
version.

This library is specifically intended to facilitate migration from GAE
Python 2.7 to any Python 3 platform, especially GAE Python 3. While any
Datastore user can download and use the NDB library, our recommendation for
new apps is still to use the Cloud Client Datastore library bundled with
the Google Cloud SDK.

Please send feedback or feature requests by opening an issue on our GitHub
repo, by responding to this email or by reaching out directly to me at
gorces...@google.com.

Due to differences in the programming environment between GAE Python 2.7
and our Python 3 runtime, we cannot be 100% compatible in all cases,
especially where there was unexpected or unclear behavior in the 2.7
library. However, we will make every effort to be compatible where possible
and document any differences while not. If you run into any incompatibility
or missing feature that is not explicitly called out in MIGRATION_NOTES.md,
please let us know. Also let us know if you run into an issue that is
called out in the migration notes but impacts you in a way we might not
have expected, or you have suggestion for a workaround or fix.

Finally, please keep in mind that this project is still in active
development and is not yet suitable for use in a production environment.

Thanks for your continued support of our platform. I am looking forward to
hearing from the community on this and upcoming efforts.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgF%2Bj-T1RTKg1EYWddpWwk3wDsE4PcY2DHDBXr79O%3DP05JA%40mail.gmail.com.

[google-appengine] Re: App Engine Basic Scaling

[Andrew Hoy]

Hey Omair,

Appreciate you getting back to me.

Great, this is exactly what I wanted to use basic scaling for - thanks for 
confirming. I Have reported the bug on the issue tracker.

On Wednesday, November 28, 2018 at 10:23:06 PM UTC, Omair (Cloud Platform 
Support) wrote:
>
> Hi Andrew,
>
> You are using basic scaling which is different from manual scaling. In 
> basic scaling instances are created on demand to handle request and 
> automatically turned down when idle. The maximum number of instances that 
> can be created is defined in the max_instances parameter. To read about 
> types of scaling available in App Engine Standard please visit the link on 
> [1]. Having said that, it does seem like a bug to me that the maximum 
> instances is showing as auto. You can report this on  Issue Tracker 
> <https://issuetracker.google.com/issues/new?component=187191=1162848>
>  
> as a bug. 
>
>
>
> [1]
> https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed#instance_scaling
>
>
> On Wednesday, November 28, 2018 at 9:57:30 AM UTC-5, Andrew Hoy wrote:
>>
>> Hi all,
>>
>> I have a query regarding max_instances when using basic scaling in the 
>> App Engine Standard environment (Node.js). Im my app.yaml file, I set 
>> max_instances to 1. This appears in the config section under App Engine > 
>> Versions in this UI:
>>
>> runtime: nodejs8
>> env: standard
>> instance_class: B4_1G
>> handlers:
>>   - url: '.*'
>> script: auto
>> basic_scaling:
>>   idle_timeout: 600s
>>   max_instances: 1
>> network: {}
>>
>> All of the above looks correct. However, when I add the 'Max Instances' 
>> column, the value is set to 'auto' (see attachment). Can someone please let 
>> me know what I'm doing wrong here? Why is the UI showing 'auto' even though 
>> the config section shows max_instances set to 1?
>>
>>
>> Thanks,
>>
>> Andy
>>
>

-- 
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/d1b42ef1-3246-4044-9b0c-0d3a748c33ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine Basic Scaling

[Andrew Hoy]

Hi all,

I have a query regarding max_instances when using basic scaling in the App 
Engine Standard environment (Node.js). Im my app.yaml file, I set 
max_instances to 1. This appears in the config section under App Engine > 
Versions in this UI:

runtime: nodejs8
env: standard
instance_class: B4_1G
handlers:
  - url: '.*'
script: auto
basic_scaling:
  idle_timeout: 600s
  max_instances: 1
network: {}

All of the above looks correct. However, when I add the 'Max Instances' 
column, the value is set to 'auto' (see attachment). Can someone please let 
me know what I'm doing wrong here? Why is the UI showing 'auto' even though 
the config section shows max_instances set to 1?


Thanks,

Andy

-- 
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/b64f825a-9a2f-4a21-b935-c2bfedc3a217%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Lots of 502 errors

[Andrew Benton]

I'm not sure how much this has to do specifically with the application in 
question, but an otherwise well-functioning appengine app will start seeing 
lots and lots of 502 errors from Google on occasion.

This is extremely disruptive to the app's users and requires some manual 
data cleanup each time, which is frustrating. There are no logging 
indicators that show these 502 responses, so I can only presume that the 
response is generated upstream from the application's infrastructure.

Any idea what's going on? Here is some more information about the app:

It's a golang app running on the flexible environment.
It uses a custom domain, with cname pointing to ghs.googlehosted.com.
It relies on the appengine datastore, although even requests to handlers 
that make no datastore connections are failing with 502.

I feel like this is a routing/timeout problem between ghs.googlehosted.com 
and the appengine infrastructure, given the lack of logging. Can anyone 
from Google comment on that hypothesis?

-- 
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/2f40a136-04c6-43df-a708-d612730d3345%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Downloading Logs

['Andrew Teall' via Google App Engine]

Hi,
Over the past couple weeks we've started recieving this error message when 
trying to download logs from appengine:

2017-04-06 18:26:55,961 INFO appcfg.py:1116 Request with offset None. 
2017-04-06 18:26:56,898 INFO appengine_rpc_httplib2.py:303 Too many retries 
for url 
https://appengine.google.com/api/request_logs?app_id=myflashpanel_vhost=False=1000=default_header=1=0=a
 
Error 500: --- begin server output ---


Server Error (500)

A server error has occurred.
--- end server output ---


How can we remedy it and prevent it from happening in the future. I've 
already turned off the process that gathers these logs.

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/40e59353-41be-45d8-8af0-423ccf8416fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Datastore get_or_insert in Java

[Andrew Buck]

The Datastore Python API has a get_or_insert() method that will atomically 
insert an entity if it doesn't exist or return the existing one if it does. 
I can't find the equivalent in Java. Does the Java API have a way of 
accomplishing this same functionality atomically?

-- 
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/85c7153f-f813-4416-aa75-e2db4b119130%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine Flexable: ImportError: No module named PLACEHOLDER

[Andrew Wilson]

Here is the raw stack trace:

Traceback (most recent call last):
  File 
"/home/vmagent/python_vm_runtime/google/appengine/ext/vmruntime/meta_app.py", 
line 550, in GetUserAppAndServe
app, mod_file = self.GetUserApp(script)
  File 
"/home/vmagent/python_vm_runtime/google/appengine/ext/vmruntime/meta_app.py", 
line 411, in GetUserApp
app = _AppFrom27StyleScript(script)
  File 
"/home/vmagent/python_vm_runtime/google/appengine/ext/vmruntime/meta_app.py", 
line 271, in _AppFrom27StyleScript
app, filename, err = wsgi.LoadObject(script)
  File "/home/vmagent/python_vm_runtime/google/appengine/runtime/wsgi.py", line 
85, in LoadObject
obj = __import__(path[0])
ImportError: No module named PLACEHOLDER


After a recent deploy to AppEngine flexable i get this spammed in the server 
logs. 

I have a very simple app.yaml - 


runtime: python27
vm: true
threadsafe: true
entrypoint: gunicorn -b :$PORT main:app


I have no idea why this is coming up or even how to start debugging. Any help 
would be greatly appriciated. Thank you


-- 
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/b78dabdf-ad15-408a-bee8-6284e5a2da0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] After app deploy on felxable environemnt: ImportError: No module named PLACEHOLDER

[Andrew Wilson]

Error in logs:

ImportError: No module named PLACEHOLDER

   1. 
  1. at LoadObject (
  /home/vmagent/python_vm_runtime/google/appengine/runtime/wsgi.py:85)
   2. 
  1. at _AppFrom27StyleScript (
  
/home/vmagent/python_vm_runtime/google/appengine/ext/vmruntime/meta_app.py:271 
  

  )
  2. at GetUserApp (
  
/home/vmagent/python_vm_runtime/google/appengine/ext/vmruntime/meta_app.py:411 
  

  )
  3. at GetUserAppAndServe (
  
/home/vmagent/python_vm_runtime/google/appengine/ext/vmruntime/meta_app.py:550 
  

  )
  4. 
  3. AppEngine Flexable enviornment. 
   4. Very simple app.yaml
   5. 
   
runtime: python27
vm: true
threadsafe: true
entrypoint: gunicorn -b :$PORT main:app

I have no idea how to debug or what might be causing the issue. 

Thanks for any help!  

   

   

   

-- 
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/0226da6d-f433-484d-933d-31f40da21443%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] LONG time to deploy into flexible hosting environment

[Andrew Rea]

I have downloaded both the GOLANG and the Python examples for the flexible 
hosting environments, using the gcloud application and setting vm: true 
inside the app.yaml.

With Python


It takes around 10 minutes to deploy.  You see all the logs until it gets 
to the "Updating Service" and then no more feedback apart from a 10 minute 
wait until it succeeds

With GO
---

It takes around 10 minutes and then it fails saying that there was an error 
deploying, the app code may not be in a healthy state. 

*My question is, *why does the deployment to the Flexible Hosting 
Environment take so long and is there anything I can do to make it takes 
seconds rather than minutes?

thanks

-- 
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/c0bcf3ee-55d1-45d2-bd6a-b5b590e1cce0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Linux Remote Desktop?

[Andrew Irwin]

I can not figure out what I'm doing wrong, but I've tried a number of 
different Linux desktop remote clients, and have also tried mapping the 
xhost DISPLAY, however nothing I do is yielding a desktop? I just need to 
be able to connect to my x Windows and I've already loaded the GNOME & KDE 
desktop environments.

-- 
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/d65a6c23-5f45-4e93-a949-ab4a3725fc1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] AppEngine with Endpoints

[Andrew James]

>From the tutorials I have seen, you can package html/css within an 
Endpoints app, effectively creating a dynamic web app. Is this good 
practise, or is the recommended approach to create a separate app 
(containing the front-end code) and host it in app engine?

-- 
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/4200493e-31d5-4e40-8598-44fb2954b8a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore Writes being Disabled

[Andrew Watson]

I'm getting that too on one of my projects!  I re-enable writes and then it 
just gets disabled again.

On Thursday, May 19, 2016 at 8:23:42 PM UTC-4, Daniel Young wrote:
>
> I've gone into the Datastore Console and it seems the writes are being 
> disabled automatically (or a message is being displayed).  I have not 
> stopped write via Datastore Admin.  Anyone else experiencing this before I 
> post an issue?
>

-- 
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/6b28e001-1314-4543-a8b3-e7478b8c2801%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: my git repo is empty

[Andrew Arrow]

thanks Nick! That worked. I have all my code now. You are an excellent googler.

On Tue, May 3, 2016 at 12:01 PM, 'Nick (Cloud Platform Support)' via
Google App Engine <google-appengine@googlegroups.com> wrote:
> Hey Andrew,
>
> So, we've taken a look at your repo internally and this is what we found:
> The Cloud Source Repository for the app was created in September (at project
> creation). It does not appear that it was ever connected to anything (commit
> from a local git repo, connected to github or bitbucket) (Source Repos
> populate from git commits / pushes). However, you should still be able to
> download any existing, uploaded apps, regardless of source repository. We
> tested with an app that was last updated in June:
>
> $ python ~/src/google_appengine/appcfg.py download_app -A $APPID -M $MODULE
> -V $VERSION .
>
> For this case:
>
> $ python ~/src/google_appengine/appcfg.py download_app -A static-1064 -M
> default -V 1 .
>
> Let me know if that works for you, and I'll be happy to assist further if
> not.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Friday, March 25, 2016 at 7:18:16 PM UTC-4, Andrew Arrow wrote:
>>
>> my site has been running for a year at:
>>
>> https://static-1064.appspot.com/
>>
>> I went to clone the repo:
>>
>> https://source.developers.google.com/p/static-1064/r/default
>>
>> and it clones an empty repo. Where's my code?
>>
> --
> 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/WCz0JORRoQ0/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/38225251-3daa-4ac7-8dcc-c582c675278b%40googlegroups.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/CANPS%3DEwzzQy5zTmdj-gJ%2BKWOt5fa%2BvES8J_zmN%2B-qg%2Bx0QYcHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: my git repo is empty

[Andrew Arrow]

sure,

~/dev $ gcloud beta source repos clone --verbosity debug default
DEBUG: Running gcloud.beta.source.repos.clone with
Namespace(__calliope_internal_deepest_parser=ArgumentParser(prog='gcloud.beta.source.repos.clone',
usage=None, description='*(BETA)* Clone project git repository in the
current directory.', version=None, formatter_class=, conflict_handler='error', add_help=False),
account=None, authority_selector=None, authorization_token_file=None,
cmd_func=>,
command_path=['gcloud', 'beta', 'source', 'repos', 'clone'],
configuration=None, credential_file_override=None, document=None,
dry_run=False, dst=None, format=None, h=None, help=None,
http_timeout=None, log_http=None, project=None, quiet=None,
src='default', trace_email=None, trace_log=None, trace_token=None,
user_output_enabled=None, verbosity='debug', version=None).
DEBUG: Executing ['git', 'clone',
'https://source.developers.google.com/p/static-1064/r/default',
'/Users/aa/dev/default', '--config', 'credential.helper="gcloud.sh"']
Cloning into '/Users/aa/dev/default'...
warning: You appear to have cloned an empty repository.
Checking connectivity... done.
Project [static-1064] repository [default] was cloned to
[/Users/aa/dev/default].
INFO: Display format "default".



On 3/30/16, 'Nick (Cloud Platform Support)' via Google App Engine
<google-appengine@googlegroups.com> wrote:
> Hey Andrew,
>
> After attempting a cursory examination, we've determine we'll need more
> info to ensure we're looking at the right parts of the system. Can you
> attempt to clone the repository (gcloud beta source repos clone
> <https://cloud.google.com/sdk/gcloud/reference/beta/source/repos/clone>)
> with `--verbosity debug` flag and reply with the output?
>
> Regards,
>
> Nick
> Cloud Platform Community Support
>
> On Saturday, March 26, 2016 at 12:11:09 PM UTC-4, Andrew Arrow wrote:
>>
>> also empty. I think during a transition from old app engine to new
>> gcloud google lost my code? I want to submitt a support request but
>> I'm on free plan.
>>
>>
>> On 3/26/16, Mihail Russu <mih...@russu.net> wrote:
>> >>Where's my code?
>> > Check the Downloading source code
>> > <
>> https://cloud.google.com/appengine/docs/python/tools/uploadinganapp#Python_Downloading_source_code>
>>
>>
>> > section
>> > to see if it'll help...
>> >
>> > On Saturday, March 26, 2016 at 1:18:16 AM UTC+2, Andrew Arrow wrote:
>> >>
>> >> my site has been running for a year at:
>> >>
>> >> https://static-1064.appspot.com/
>> >>
>> >> I went to clone the repo:
>> >>
>> >> https://source.developers.google.com/p/static-1064/r/default
>> >>
>> >> and it clones an empty repo. Where's my code?
>> >>
>> >>
>> >
>> > --
>> > 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/WCz0JORRoQ0/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/5e58dc33-0d0d-4c43-8719-f0c4df7f6638%40googlegroups.com.
>>
>>
>> > For more options, visit https://groups.google.com/d/optout.
>> >
>>
>
> --
> 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/WCz0JORRoQ0/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/1554602c-3b85-4a1a-8f75-29a5f05000e3%40googlegroups.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/CANPS%3DEyBJ74b_-OqArVjT_ktKPWOzbVbLLqH-aFHLcn0_bcx5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: my git repo is empty

[Andrew Arrow]

also empty. I think during a transition from old app engine to new
gcloud google lost my code? I want to submitt a support request but
I'm on free plan.


On 3/26/16, Mihail Russu <mih...@russu.net> wrote:
>>Where's my code?
> Check the Downloading source code
> <https://cloud.google.com/appengine/docs/python/tools/uploadinganapp#Python_Downloading_source_code>
> section
> to see if it'll help...
>
> On Saturday, March 26, 2016 at 1:18:16 AM UTC+2, Andrew Arrow wrote:
>>
>> my site has been running for a year at:
>>
>> https://static-1064.appspot.com/
>>
>> I went to clone the repo:
>>
>> https://source.developers.google.com/p/static-1064/r/default
>>
>> and it clones an empty repo. Where's my code?
>>
>>
>
> --
> 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/WCz0JORRoQ0/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/5e58dc33-0d0d-4c43-8719-f0c4df7f6638%40googlegroups.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/CANPS%3DExQAVC8s-EKRVY2vKnOyX1LNWjMmB7sVcJpf9zrHrJE4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] my git repo is empty

[Andrew Arrow]

my site has been running for a year at:

https://static-1064.appspot.com/

I went to clone the repo:

https://source.developers.google.com/p/static-1064/r/default

and it clones an empty repo. Where's my code?

-- 
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/58792daa-27db-478c-8ccb-94b2bc4b8171%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.

Re: [google-appengine] Docker cache issue when deploying GO to Managed VM using Cloud Shell and aedeploy

['Andrew Jessup' via Google App Engine]

Thanks, we'll clear up the documentation to make it clearer. In the
meantime, here's a quick explanation. The difference between the two modes
is the way builds are performed.

In the current (default) way, a transient GCE VM (called the builder VM) is
provisioned in your project, which runs the Docker build. The gcloud tool
uses the Docker wire protocol to connect to the GCE VM to perform the
build. This usually works well for most customers, but has some
disadvantages. The most notable are:

   - GCE VMs can take a few seconds (~30) to be provisioned, which adds
   that much delay to the overall deployment time

   - There are some edge cases where GCE VM deployments fail (for example,
   the one you just encountered, or when certain GCE quotas are exceeded)
   which then causes the failure of the App Engine deployment.

   - As a customer, you will see transient builder VMs in your project
   (which can be annoying to have to parse through)

The container builder service addresses these concerns, by performing
builds via a dedicated service. This avoids both the 30s VM provisioning
delay and the issues associated with transient VMs. It also allows us to
more easily improve and optimize the build experience over time. Overall
deployments on Managed VMs should thus be faster and more reliable.

We are working to make Container Builder the default underlying mechanism
for Managed VM deployments. We have a few teething issues to sort out
(mainly relating to how the service is activated) before we do that, but
I'd encourage all interested customers to try it out using the gcloud
configuration setting described above. Please also make sure you're using
the latest release (96.0.0 or later) of the gcloud tool as that includes
some important updates.

And if you're trying out, please give us feedback! If you'd prefer you can
reach me directly - jessup AT google DOT com.

On Tue, Feb 16, 2016 at 9:09 PM, Roy Palacios <roy.palac...@cpe.pe> wrote:

> Hi Andrew,
>
> Thanks for the response. It looks like it is working perfectly :)
>
> I see it documented here as well:
> https://cloud.google.com/appengine/docs/managed-vms/go/testing-and-deploying-your-app
>
> However, it's not really clear what the advantage is. Both methods run
> remotely (the first one is a transient VM).
>
> Thanks,
> Roy
>
> On Tue, Feb 16, 2016 at 11:38 PM, 'Andrew Jessup' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> Hi Roy,
>>
>> You can try using the container builder
>> <https://cloud.google.com/container-builder/docs/> API to run your image
>> builds in App Engine (rather than relying on the local docker
>> installation). To do this, run:
>>
>> $ gcloud config set app/use_cloud_build true
>>
>> Then try a deployment again using aedeploy.
>>
>>
>>
>> On Tue, Feb 16, 2016 at 7:32 PM, Roy Palacios <roy.palac...@cpe.pe>
>> wrote:
>>
>>> Hello,
>>>
>>> I have a Go project running on ManagedVMs and wanted to try the Cloud
>>> Shell.
>>>
>>> So, I have my repository in $HOME/default and a symbolic link from my
>>> repository to $GOPATH
>>>
>>> The problem is that whenever I pull changes from the Cloud Shell and try
>>> to deploy with aedeploy, I end up using the Docker Cache and the changes
>>> are not reflected.
>>>
>>> I guess it is because somehow the build process didnt detect the changes.
>>>
>>> Is there anything to fix this? My workaround now is just to do some
>>> dummy code change using the Cloud Shell.
>>>
>>> Thanks,
>>> Roy
>>>
>>> roy_palacios@sanguine-form-95600:~/default/
>>> xxx.pe/module/batch$ git pullUnpacking objects: 100% (6/6),
>>> done.From
>>> https://source.developers.google.com/p/sanguine-form-95600/r/default
>>> 8fd0d40..08c487b master -> origin/masterUpdating 8fd0d40..08c487b
>>> Fast-forward cpe.pe/batch/padronbatch/padronbatch.go | 9 + 1
>>> file changed, 9 insertions(+)roy_palacios@sanguine-form-95600:~/default/
>>> xx.pe/module/batch$ aedeploy gcloud preview app deploy app.yamlYou
>>> are about to deploy the following modules: - sanguine-form-95600/batch
>>> (from [/tmp/aedeploy433757798/app.yaml]) Deployed URL:
>>> [x]Do you want to continue (Y/n)? yBeginning
>>> deployment...Verifying that Managed VMs are enabled and ready.Building
>>> and pushing image for module 
>>> [batch]
>>> DOCKER BUILD OUTPUT
>>> 

Re: [google-appengine] Docker cache issue when deploying GO to Managed VM using Cloud Shell and aedeploy

['Andrew Jessup' via Google App Engine]

Hi Roy,

You can try using the container builder
<https://cloud.google.com/container-builder/docs/> API to run your image
builds in App Engine (rather than relying on the local docker
installation). To do this, run:

$ gcloud config set app/use_cloud_build true

Then try a deployment again using aedeploy.



On Tue, Feb 16, 2016 at 7:32 PM, Roy Palacios <roy.palac...@cpe.pe> wrote:

> Hello,
>
> I have a Go project running on ManagedVMs and wanted to try the Cloud
> Shell.
>
> So, I have my repository in $HOME/default and a symbolic link from my
> repository to $GOPATH
>
> The problem is that whenever I pull changes from the Cloud Shell and try
> to deploy with aedeploy, I end up using the Docker Cache and the changes
> are not reflected.
>
> I guess it is because somehow the build process didnt detect the changes.
>
> Is there anything to fix this? My workaround now is just to do some dummy
> code change using the Cloud Shell.
>
> Thanks,
> Roy
>
> roy_palacios@sanguine-form-95600:~/default/
> xxx.pe/module/batch$ git pullUnpacking objects: 100% (6/6),
> done.From
> https://source.developers.google.com/p/sanguine-form-95600/r/default
> 8fd0d40..08c487b master -> origin/masterUpdating 8fd0d40..08c487b
> Fast-forward cpe.pe/batch/padronbatch/padronbatch.go | 9 + 1 file
> changed, 9 insertions(+)roy_palacios@sanguine-form-95600:~/default/
> xx.pe/module/batch$ aedeploy gcloud preview app deploy app.yamlYou
> are about to deploy the following modules: - sanguine-form-95600/batch
> (from [/tmp/aedeploy433757798/app.yaml]) Deployed URL: [x]Do
> you want to continue (Y/n)? yBeginning deployment...Verifying that
> Managed VMs are enabled and ready.Building and pushing image for module
> [batch]
> DOCKER BUILD OUTPUT
> -Step
> 1 : FROM gcr.io/google_appengine/golang---> 28d7c86afc7aStep 2 : COPY .
> /go/src/app---> Using cache---> 9e8c6f93f56cStep 3 : RUN go-wrapper
> install -tags appenginevm---> Using cache---> 6693827d78cdSuccessfully
> built 6693827d78cd
> --Copying
> files to Google Cloud Storage...Synchronizing files to [gs://
> staging.sanguine-form-95600.appspot.com/].Updating module 
> [batch]...done.Deployed
> module [batch] to [xx]
>
> --
> 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/2e8f6844-3f7b-45ba-973d-9ab89e1a8ada%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/2e8f6844-3f7b-45ba-973d-9ab89e1a8ada%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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/CAEF6f2vo-QPCOqwcyu_D_nBZRBshtTXXjNmERCQT9%3D0QB%3DotjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Taskqueue INVALID_REQUEST error in pull queues

[Andrew Haskell]

I'm using a pull queue in Appengine for Go and while locally leasing tasks 
worked just fine, when I deployed my code, the call to taskqueue.Lease gave 
me this error:

API error 13 (taskqueue: INVALID_REQUEST) *internal.APIError

My lease call was:

tasks, err := taskqueue.Lease(ctx, 100, "pullqueue", 60)

And it has happened no matter what parameters I pass in, like parameters 
for a blank queue name. Has anyone else gotten this error? Thanks in 
advance for the help!

-- 
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/30626d8e-9144-42fa-bd5b-4da3d563e797%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Taskqueue INVALID_REQUEST error in pull queues

[Andrew Haskell]

Nvm in my real code I was leasing 2000 tasks but the max I can lease is 
actually 1000.

On Tuesday, January 12, 2016 at 12:49:52 PM UTC-5, Andrew Haskell wrote:
>
> I'm using a pull queue in Appengine for Go and while locally leasing tasks 
> worked just fine, when I deployed my code, the call to taskqueue.Lease 
> gave me this error:
>
> API error 13 (taskqueue: INVALID_REQUEST) *internal.APIError
>
> My lease call was:
>
> tasks, err := taskqueue.Lease(ctx, 100, "pullqueue", 60)
>
> And it has happened no matter what parameters I pass in, like parameters 
> for a blank queue name. Has anyone else gotten this error? Thanks in 
> advance for the help!
>

-- 
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/b43dbe65-21b1-4bc7-9d4e-ae8d82f20f05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Sign up now for access to faster, more reliable builds on Managed VMs

[Andrew Jessup]

Hello!

Earlier in the year we added remote builds to Managed VMs, which uses a 
transient GCE VM to build and package your application in Google Container 
Registry, prior to deploying it to App Engine.

We’ve been working hard to improve this functionality, and today we’re 
pleased to announce an alpha release of a new build backend for Managed VMs 
that is purpose-built for building applications quickly and reliably. 

Since this back-end doesn’t rely on creating GCE VMs in your project, it 
has some advantages. 

   - It is generally faster (since we don’t need to create a VM ahead of 
   time), and
   - Doesn’t add transient GCE VMs for building to your project, and 
   - It doesn’t consume GCE usage quotas (such as network per project)
   
We will be improving the performance of this service even more over the 
next few months.

To get started with this API, you must be whitelisted to use the service, 
which you can request by completing this form . 
Whitelisting is conducted on a per-user basis. Once you have been 
whitelisted we will e-mail you instructions on how to get started with the 
service. If you’d like to learn more about this service, feel free to reach 
out to me directly.

Thanks,

The App Engine Team

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cefaa491-bd40-404c-b544-3567f170cdb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Announcing SSL for GAE Custom Domains in the Developers Console

[Andrew Greene]

SSL on naked domains work. Add the A and  records.

Then go to the dev console. Click on SSL Certs, then click the box next to 
your naked domain. It works!

On Wednesday, September 16, 2015 at 7:07:14 PM UTC-4, husayt wrote:
>
> Hi Lorne,
>
> naked domains been mentioned here, which is a big problem. We really need 
> to get that resolved. Also naked domains for GCS hosted static websites 
> (Non ssl, since ssl is not available there) is a huge issue.
>
> Would be great if  Google would support SSL and naked domains on all range 
> of different hosting options provided. This is just necessary.
>
> Thanks
>
> On Wednesday, September 16, 2015 at 6:33:54 PM UTC+1, Lorne Kligerman 
> wrote:
>>
>> Thanks for all the quick feedback!  No downtown was expected or took 
>> place during this migration and launch.  The work involved here didn't 
>> touch the basics of how the applications are being served, but just the 
>> configuration.
>>
>> @PK, good catch on the reference to the old UI, we'll get that cleaned up 
>> right away.
>>
>> @Jeff, the set of domains each administrator can view are those that they 
>> have personally verified.
>>
>> We're looking into solutions for the naked domain issue, stay tuned for 
>> more details.
>>
>> Cheers,
>> Lorne.
>>
>>
>>
>>
>>
>> On Wednesday, September 16, 2015 at 2:36:09 AM UTC-7, Panayiotis 
>> Lipiridis wrote:
>>>
>>> oki.. that worked, I just had to add it to the list. But is it possible 
>>> to redirect automatically to www as it does with the http (no SSL works)?
>>>
>>> We used to have that setting under Google Apps for Work console.. but 
>>> now I cannon find it in the new one. Where do we setup the automatic 
>>> redirects for naked domains?
>>>
>>> On Wednesday, September 16, 2015 at 10:31:01 AM UTC+2, Panayiotis 
>>> Lipiridis wrote:

 I didn't find out how could I redirect from naked SSL domain to www for 
 example.

 (https://example.com >> https://www.example.com)

 On Wednesday, September 16, 2015 at 4:19:06 AM UTC+2, Darshan-Josiah 
 Barber wrote:
>
> Nope, that wasn't the issue; it was already taken care if in step 7.  
> However, for whatever reason, everything is working now!
>


-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0885af80-a8ce-4e13-98c9-f4feec819e61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Unable to access new App Engine Developers Console with particular app

[Andrew Vaslas]

Hello,

I have been working with App Engine for several years, and I have several 
apps that I have kept alive over that period. Oddly, I have one app that I 
cannot access in the new Developers Console. I can access this app (along 
with all of my other apps) in the original Dev Console, but when I try to 
access it in the new console by clicking on the hints that pop up 
encouraging me to check out the new console, I am brought to the new 
console with a message saying, The project you requested is unavailable. 
Also, this particular project does not appear in the Select a project 
dropdown on the new console.

This is a major issue for me, as I cannot manage API access, permissions, 
and many other core features for my App Engine app on the old console. 
Support folks, any idea what's up?

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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ec794cba-dfa8-4a7c-9bbb-3bb9b5ff1151%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: gcloud preview app run ./app.yaml error with python managed VMs

[Andrew Jessup]

Hey Cryril - this sounds like a bug. Would you mind reporting this on our 
issue tracker? https://code.google.com/p/googleappengine and we'll follow 
up there.

On Thursday, 13 August 2015 07:41:34 UTC-7, Cyril MORISSE wrote:

 Hello,

 I'm a beginner with Appengine / Python and I work on OSX Yosemite.

 I'm following the Managed VM Python tutorial: 
 https://cloud.google.com/appengine/docs/managed-vms/tutorial/step1
 I'm at step 6 and everything is Ok.

 But there is something I don't understand.
 - Deployment with gcloud preview app deploy ./app.yaml is Ok
 - Deployment with gcloud preview app run ./app.yaml is Ok if I export 
 GAE_LOCAL_VM_RUNTIME=0.  In that case, my app is running in a local 
 container (version 1.7) and I can access it.

 *But I'm struggling with: gcloud preview app run ./app.yaml *when 
 GAE_LOCAL_VM_RUNTIME is undefined or set to 1.

 In that case launch is OK.

 cmorisse@dueto:appengine-vm-fortunespeak-python$ gcloud preview app run ./
 app.yaml
 Module [default] found in file [/Users/cmorisse/dev-inouk/appengine/
 appengine-vm-fortunespeak-python/app.yaml]
 INFO: Looking for the Dockerfile in /Users/cmorisse/dev-inouk/appengine/
 appengine-vm-fortunespeak-python
 INFO: Using Dockerfile found in /Users/cmorisse/dev-inouk/appengine/
 appengine-vm-fortunespeak-python
 INFO 2015-08-13 13:41:07,025 application_configuration.py:399] No 
 version specified. Generated version id: 20150813t134107
 INFO 2015-08-13 13:41:07,025 devappserver2.py:763] Skipping SDK 
 update check.
 INFO 2015-08-13 13:41:07,056 api_server.py:205] Starting API server at
 : http://localhost:50839
 INFO 2015-08-13 13:41:07,061 dispatcher.py:197] Starting module 
 default running at: http://localhost:8080
 INFO 2015-08-13 13:41:07,063 admin_server.py:118] Starting admin 
 server at: http://localhost:8000
 INFO 2015-08-13 13:41:08,073 module.py:1767] New instance for module 
 default serving on:
 http://localhost:8080
 INFO 2015-08-13 13:41:08,500 module.py:809] default: GET /_ah/start 
 HTTP/1.1 404 233



 *But when I access http://localhost:8080 http://localhost:8080, I get:*

 ERROR2015-08-13 13:44:56,125 app.py:1423] Exception on / [GET]
 Traceback (most recent call last):
   File 
 /Users/cmorisse/dev-inouk/appengine/appengine-vm-fortunespeak-python/lib/flask/app.py
 , line 1817, in wsgi_app
 response = self.full_dispatch_request()
   File 
 /Users/cmorisse/dev-inouk/appengine/appengine-vm-fortunespeak-python/lib/flask/app.py
 , line 1477, in full_dispatch_request
 rv = self.handle_user_exception(e)
   File 
 /Users/cmorisse/dev-inouk/appengine/appengine-vm-fortunespeak-python/lib/flask/app.py
 , line 1381, in handle_user_exception
 reraise(exc_type, exc_value, tb)
   File 
 /Users/cmorisse/dev-inouk/appengine/appengine-vm-fortunespeak-python/lib/flask/app.py
 , line 1475, in full_dispatch_request
 rv = self.dispatch_request()
   File 
 /Users/cmorisse/dev-inouk/appengine/appengine-vm-fortunespeak-python/lib/flask/app.py
 , line 1461, in dispatch_request
 return self.view_functions[rule.endpoint](**req.view_args)
   File 
 /Users/cmorisse/dev-inouk/appengine/appengine-vm-fortunespeak-python/main.py
 , line 11, in fortune
 msg = subprocess.check_output('fortune')
 AttributeError: 'module' object has no attribute 'check_output'

 It seems to me, that my program is running within the sandboxed SDK that 
 explains check_output is unavailable.

 I'm surprised as I would think that with these lines in my app.yaml
 runtime: python27
 vm: true
 then gcloud preview app run ./app.yaml will do a dockerless build and 
 run my app locally without the
 constraints of the sandboxed app.

 Any idea about what I'm missing ?

 Thanks,
 Cyril


-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eb9c6779-288c-4f00-ab95-49d871afc867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Upcoming changes to App Engine support in the Google Cloud SDK

[Andrew Jessup]

Hi Karl, thanks for reaching out - there seems to be some understandable 
confusion around this announcement, I've added a few responses inline.

On Wednesday, 8 July 2015 07:42:53 UTC-7, Karl MacMillan wrote:

  Hey Andrew - a few questions.
  
  On Jul 8, 2015, at 3:16 AM, 'Andrew Jessup' via Google App Engine 
 google-a...@googlegroups.com javascript: wrote:

  Hi folks,

 We're making an important change to the Google Cloud SDK to simplify how 
 App Engine developers can access and work with the SDK.

 As of the next release, 0.9.68, of the Google Cloud SDK - we will no 
 longer be distributing the stand alone App Engine SDKs. 

  
 Can you give us a timeframe for this release? Many of us probably have 
 some automation around these tools (I certainly do) and it would be nice to 
 be able to plan when we need to make the changes. Especially as this kind 
 of work provides no benefit for me or my users, so it’s not a high priority.


We expect this release to be available in the next couple of days, although 
occasionally delays come up.

I absolutely hear you that this is a pain for automation. We're aiming to 
minimize breaking changes once we remove the 'preview' label from the 
gcloud app command, which is why we're doing this now. In the interim, the 
version pinning described below is one way to minimize the effect/surprise 
changes when using the Google Cloud SDK.
 


 Also - I just had some interaction with the support team over the urlfetch 
 bug and they were discussing which of the next two GAE SDK releases the bug 
 might be fixed in. Does that mean that there are going to be at least two 
 more releases of the stand-alone SDK? Or does this announcement change 
 that? 


We're going to keep distributing the stand-alone SDKs (that is the SDKs not 
shipped in gcloud) for the forseeable future, this announcement doesn't 
affect them. What this refers to is the copy of appcfg.py/.sh and and 
dev_appserver.py/.sh that are bundled with the Google Cloud SDK.
 


 Basically - I don’t quite understand how the release schedule of what (to 
 me) are two different SDKs interact. Heck - I’m not even quite clear on how 
 these two SDKs are intended to interact at all (more on that below).

  The gcloud preview app deploy and gcloud preview app run commands that 
 most developers use within gcloud will continue to work, users should not 
 notice any obvious change.

  
 You say that most users use the gcloud commands, but I find that very hard 
 to believe. All of your docs point to the old tools (e.g., 
 https://cloud.google.com/appengine/docs/python/gettingstartedpython27/uploading
  
 and https://cloud.google.com/appengine/docs/java/tools/uploadinganapp). 
 Also your gcloud docs explicitly state that these tools are beta and not 
 covered by “any SLA or deprecation policy and may be subject to 
 backward-incompatible changes” (https://cloud.google.com/sdk/gcloud-app).


Ah, there might be some confusion here. I was referring to the fact that 
most users *of the Google Cloud SDK https://cloud.google.com/sdk/* to 
interact with GAE are using gcloud app run/deploy rather than the 
appcfg.py/dev_appserver.py commands.

However, you're quite right - most users of App Engine right now are not 
yet using the Google Cloud SDK at all, but are using the stand-alone App 
Engine SDKs https://cloud.google.com/appengine/downloads and are using 
the appcfg.py/.sh and dev_appserver.py/.sh commands from there. Fortunately 
these folks aren't affected by this announcement, this only applies to 
those using appcfg.py/.sh and dev_appserver.py/.sh *from the Google Cloud 
SDK*.

Using the stand-alone App Engine SDKs, and the tools therein, is still the 
recommended path for interacting with App Engine for anyone not using 
Managed VMs. 
 


 Call me a fuddy-duddy, but I tend to stick to what you guys document as 
 the correct way and avoid things that are in beta and you tell me are not 
 yet supported. Needless to say I’m surprised and annoyed for this casual 
 message from you to change all of that without any change to the public 
 documentation. 


 Also, will these continue to be under the preview command (which I 
 understood to mean were not yet stable)? If these are going to be the only 
 supported means of interacting with GAE it seems surprising that they are 
 going to be in preview still. If they are going to change it would be nice 
 to have one release where the commands are not in preview but the 
 standalone tools are still supported to ease our migration and just in case 
 there are bugs / breaking changes. Otherwise there is no period where I can 
 migrate my automation _and_ use tools that are officially supported.


We will continue shipping the current (non-beta) tooling using the 
stand-alone SDKs as we currently do, it's only distribution via gcloud that 
is affected. We plan to continue shipping these tools in stand-alone SDKs 
for the forseeable future.
 


  For users who were directly using

Re: [google-appengine] Upcoming changes to App Engine support in the Google Cloud SDK

['Andrew Jessup' via Google App Engine]

Hey Karl,

1. The ambition is that we will eventually make gcloud app run/deploy the
preferred way to access App Engine for all customers (Managed VM and
regular instances), though as has been pointed out here and elsewhere we
have some work to do before we get to that point. When we do get to that
point, we'll definitely make sure we're giving folks enough time to move
over by supporting both SDKs in parallel for a decent period of time.

In the meantime, I would continue to keep using the stand alone SDKs for
the moment when working with non-managed VMs if you want the most stable
surface area (for use in integration scripts, etc.). Expect the Cloud SDK
equivalents to quickly get better.

2. Yes, it should (and in fact this recent change should make it easier).
If you run into problems let us know.



On Wed, Jul 8, 2015 at 10:43 AM, Karl MacMillan k...@rakkoon.com wrote:





  The gcloud preview app deploy and gcloud preview app run commands that
 most developers use within gcloud will continue to work, users should not
 notice any obvious change.


 You say that most users use the gcloud commands, but I find that very
 hard to believe. All of your docs point to the old tools (e.g.,
 https://cloud.google.com/appengine/docs/python/gettingstartedpython27/uploading
 and https://cloud.google.com/appengine/docs/java/tools/uploadinganapp).
 Also your gcloud docs explicitly state that these tools are beta and not
 covered by “any SLA or deprecation policy and may be subject to
 backward-incompatible changes” (https://cloud.google.com/sdk/gcloud-app).


 Ah, there might be some confusion here. I was referring to the fact that
 most users *of the Google Cloud SDK https://cloud.google.com/sdk/*to
 interact with GAE are using gcloud app run/deploy rather than the
 appcfg.py/dev_appserver.py commands.

 However, you're quite right - most users of App Engine right now are not
 yet using the Google Cloud SDK at all, but are using the stand-alone App
 Engine SDKs https://cloud.google.com/appengine/downloadsand are using
 the appcfg.py/.sh and dev_appserver.py/.sh commands from there.
 Fortunately these folks aren't affected by this announcement, this only
 applies to those using appcfg.py/.sh and dev_appserver.py/.sh *from the
 Google Cloud SDK*.

 Using the stand-alone App Engine SDKs, and the tools therein, is still the
 recommended path for interacting with App Engine for anyone not using
 Managed VMs.



 Ok - this seems to be the core of the confusion then and the handling of
 this changes makes a lot more sense to me. Two more questions then:

 1. Will everything eventually be moved into gcloud or will gcloud only be
 the recommended solution for managed VMs? In other words, will the
 stand-alone SDK eventually be replaced by the Google Cloud SDK?

 2. I assume that having both SDKs installed will work fine for those that
 need a mix of managed VMs and pure App Engine?

 Thanks - 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 http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/8B50B7DB-FD6E-46D1-9D4B-5DC9756317ED%40rakkoon.com
 https://groups.google.com/d/msgid/google-appengine/8B50B7DB-FD6E-46D1-9D4B-5DC9756317ED%40rakkoon.com?utm_medium=emailutm_source=footer
 .

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




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAEF6f2sPjBP7kRe2XOhyDOsVsnzjgsM66A7DdDvdjdB3fHaqCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Upcoming changes to App Engine support in the Google Cloud SDK

['Andrew Jessup' via Google App Engine]

Hi folks,

We're making an important change to the Google Cloud SDK to simplify how
App Engine developers can access and work with the SDK.

As of the next release, 0.9.68, of the Google Cloud SDK - we will no longer
be distributing the stand alone App Engine SDKs.

The gcloud preview app deploy and gcloud preview app run commands that most
developers use within gcloud will continue to work, users should not notice
any obvious change.

For users who were directly using appcfg.py, appcfg.sh, dev_appserver.py or
dev_appserver.sh scripts, or the GUI launchers that were bundled with the
Google Cloud SDK, you have two options:

You can continue to use the latest versions of these tools used by
installing them from the stand-alone App Engine SDKs that can be found
here: https://cloud.google.com/appengine/downloads.

In the short term, if you need to prevent this from happening, you can pin
a version of gcloud SDK with the following commands:

  gcloud config set --scope=installation
component_manager/fixed_sdk_version 0.9.67
  gcloud components update

As part of this change, the gae-java, gae-python, gae-php, and gae-go
components no longer exist in the component manager.  The `gcloud preview
app run` command will install language specific runtime libraries on
demand, as needed by your application.

If you have questions or concerns, please let us know.

Thanks,

Andrew, on behalf of the Cloud SDK team
Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAEF6f2tMjbP%3DeEcBuB5p2ubscWjsR8RHmoPUvnNopxZxydhEBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Push to deploy discontinued?

[Andrew Jessup]

Hi SS,

We've only tested this with the documentation provided at 
https://cloud.google.com/tools/repo/push-to-deploy

which describes how to create a new Jenkins instance with the appropriate 
plugins and tools already installed. You may be able to re-use a different 
Jenkins instance to work with these instructions, or update one to use the 
same plugins and tools, but we don't have instructions for doing so at this 
time.

As for unit testing instructions for PHP, we will aim to to provide some 
shortly. We will likely need to update the image described in the 
documentation to do this however since we don't install PHPUnit by default.

On Wednesday, 27 May 2015 21:59:43 UTC-7, SS wrote:

 Dear  Andrew,
 Thnks fr ur reply. We ll test it. We already have a GCE(Debian 
 Linux) running w LAMP stack.

 So, should I install the below bitnami jenkins under GCE 
 Debian platform to proceed further, since i cant use a second time 'Click 
 to deploy JENKINS' under the same GCE instance
 https://bitnami.com/stack/jenkins/installer

 Also which plugins should I use for jenkins? Should I use the 
 below one or use a specific PHP plugin fr Jenkins?
 
 https://wiki.jenkins-ci.org/display/JENKINS/Google+Source+Plugin
 http://jenkins-php.org/

 As you mentioned, should I ignore these below steps fr BUILD  
 TEST under PHP deployements:

 



 *PythonIf you have have implemented unit tests for your app, 
 do the following:Select Execute Shell.   
  Enter the following in the Command text field:   
  nosetests --with-xunit --xunit-file=nosetests.xml*

 Is so, how my PHP App will be auto built and tested(PHPUnit fr eg.) 
 like xunit in Python?

 Thnks in advance fr ur help, very eager to setup this jenkin fr our 
 dozens of PHP APP in GAE.Hope u ll help us.
 SS


 On Thursday, May 28, 2015 at 9:02:37 AM UTC+8, Andrew Jessup wrote:

 Hi SS, thanks for your patience. I've done some testing, you should be 
 able to deploy PHP applications using Jenkins by following the instructions 
 at:

 https://cloud.google.com/tools/repo/push-to-deploy

 These don't explicitly say how to deploy a PHP application, but 
 fortunately it's exactly the same as for python apps (except for the Build 
 and Test step, which will not work - but you can also safely ignore).

 We'll get the documentation updated to describe how to deploy PHP 
 applications shortly.

 On Friday, 22 May 2015 21:37:57 UTC-7, SS wrote:

 Thnks Andrew fr ur instant reply.We are waiting eagerly for this news 
 update.

 Thnks,
 Ss

 On Friday, May 22, 2015 at 10:57:34 PM UTC+8, Andrew Jessup wrote:

 Hi SS, we're testing PHP with Jenkins right now. I'll update this 
 thread as soon as we've fixed up the documentation.

 On Fri, May 22, 2015 at 4:31 AM, SS sarathbab...@ssomens.com wrote:

 Dear Brad,
   I just saw this. I have a PHP app deployed in GAE, 
 can I use JENKINS? 
 Does Jenkins supports PHP app AUTO deployment for GAE?

 Currently, I see only, JAVA, PY, GO support in the documentation.
 Can you please clear this?

 Thnks,
 Ss

 On Saturday, March 7, 2015 at 1:23:28 AM UTC+8, Brad Abrams wrote:

 We really want to enable that use case.  The infrastructure we used 
 for that in the past has proven to not meet our reliability 
 requirements, 
 so we are actively building a replacement.  As soon as that replacement 
 is 
 ready, we will re-enable this functionality.

 ..brad



 On Fri, Mar 6, 2015 at 9:18 AM Dustin Hoffmann dustin...@gmail.com 
 wrote:

 Hey Brad, my use case is this: I have a new html/css/js based single 
 page app that I am hosting on Google Cloud. The old pipeline ui is now 
 gone, and I am not a fan of Jenkins. All I want to do is have a simple 
 deploy on git push like it was previously. Is this possible for me?
  

 On Wednesday, March 4, 2015 at 11:02:03 PM UTC-6, Brad Abrams wrote:

 Thanks for following up -- I am sorry this is confusing.   

 For Java developers, we recommend you use Jenkins as we describe 
 here: 
 https://cloud.google.com/tools/repo/push-to-deploy

 does that help?

 ..brad

 On Wed, Mar 4, 2015 at 8:52 PM bergstrom...@gmail.com wrote:

 Sorry I'm a bit confused as of how to exactly deploy a project.

 For existing projects I always used git push origin master to 
 push-and-deploy. How would existing projects do that now? Will they 
 continue to work? It seems as from yesterday this stopped working 
 (but then 
 I heard that it started working again...) It would be nice to know 
 the 
 official stance on this, if it *should* work or not.

 For new projects, we just have to use Jenkins, right? Or is there 
 another way? That email, which we also received, stated that gcloud 
 app 
 update would work to deploy, but I don't think that's a working 
 command at 
 all. Please shed some light.



 On Tuesday, February 3, 2015 at 12:48:53

Re: [google-appengine] Re: Push to deploy discontinued?

[Andrew Jessup]

Hi SS, thanks for your patience. I've done some testing, you should be able 
to deploy PHP applications using Jenkins by following the instructions at:

https://cloud.google.com/tools/repo/push-to-deploy

These don't explicitly say how to deploy a PHP application, but fortunately 
it's exactly the same as for python apps (except for the Build and Test 
step, which will not work - but you can also safely ignore).

We'll get the documentation updated to describe how to deploy PHP 
applications shortly.

On Friday, 22 May 2015 21:37:57 UTC-7, SS wrote:

 Thnks Andrew fr ur instant reply.We are waiting eagerly for this news 
 update.

 Thnks,
 Ss

 On Friday, May 22, 2015 at 10:57:34 PM UTC+8, Andrew Jessup wrote:

 Hi SS, we're testing PHP with Jenkins right now. I'll update this thread 
 as soon as we've fixed up the documentation.

 On Fri, May 22, 2015 at 4:31 AM, SS sarathbab...@ssomens.com wrote:

 Dear Brad,
   I just saw this. I have a PHP app deployed in GAE, can 
 I use JENKINS? 
 Does Jenkins supports PHP app AUTO deployment for GAE?

 Currently, I see only, JAVA, PY, GO support in the documentation.
 Can you please clear this?

 Thnks,
 Ss

 On Saturday, March 7, 2015 at 1:23:28 AM UTC+8, Brad Abrams wrote:

 We really want to enable that use case.  The infrastructure we used for 
 that in the past has proven to not meet our reliability requirements, so 
 we 
 are actively building a replacement.  As soon as that replacement is 
 ready, 
 we will re-enable this functionality.

 ..brad



 On Fri, Mar 6, 2015 at 9:18 AM Dustin Hoffmann dustin...@gmail.com 
 wrote:

 Hey Brad, my use case is this: I have a new html/css/js based single 
 page app that I am hosting on Google Cloud. The old pipeline ui is now 
 gone, and I am not a fan of Jenkins. All I want to do is have a simple 
 deploy on git push like it was previously. Is this possible for me?
  

 On Wednesday, March 4, 2015 at 11:02:03 PM UTC-6, Brad Abrams wrote:

 Thanks for following up -- I am sorry this is confusing.   

 For Java developers, we recommend you use Jenkins as we describe 
 here: 
 https://cloud.google.com/tools/repo/push-to-deploy

 does that help?

 ..brad

 On Wed, Mar 4, 2015 at 8:52 PM bergstrom...@gmail.com wrote:

 Sorry I'm a bit confused as of how to exactly deploy a project.

 For existing projects I always used git push origin master to 
 push-and-deploy. How would existing projects do that now? Will they 
 continue to work? It seems as from yesterday this stopped working (but 
 then 
 I heard that it started working again...) It would be nice to know the 
 official stance on this, if it *should* work or not.

 For new projects, we just have to use Jenkins, right? Or is there 
 another way? That email, which we also received, stated that gcloud 
 app 
 update would work to deploy, but I don't think that's a working 
 command at 
 all. Please shed some light.



 On Tuesday, February 3, 2015 at 12:48:53 PM UTC+9, Brad Abrams wrote:


 Thanks for all your feedback on this change. We heard from many of 
 you that, while the Jenkins-based solution we offer works 
 https://cloud.google.com/tools/repo/push-to-deploywell for 
 larger projects with dedicated build and test steps, it works much 
 less 
 well for more simple projects with no build or test steps.  

 To that end, we are going to continue to support push to deploy for 
 existing projects that don’t require build or test.  For example, 
 python or 
 php applications code be pushed to the git repo and will be deployed 
 to app 
 engine just as it works today.  We continue to recommend jenkins 
 https://cloud.google.com/tools/repo/push-to-deployfor 
 applications that require build and test steps.


 If you have any problems with the source only deployments, please 
 do let me know. 


 Thanks again for your feedback.  

 ..brad

 On Mon Feb 02 2015 at 12:57:30 PM Syrus Mesdaghi syr...@gmail.com 
 wrote:

 At the very least you should have a one liner notice when someone 
 goes to setup a new pipeline with deploy source only mentioning that 
 it is 
 deprecated. We have a project that is still building as 'deploy 
 source 
 only'... I made a new project and have spent days trying to figure 
 out why 
 it doesn't deploy. I just happened to come across this thread in my 
 desperate attempts to figure out what is going on. I agree with Lucas 
 that 
 At least pushing source should remain as a feature. Having to do a 
 lot 
 more to do exactly what we needed doesn't feel like an upgrade though 
 I'm 
 sure some users will enjoy the extra capability.
  
 On Friday, December 19, 2014 at 6:44:30 PM UTC-5, Lucas Geiger 
 wrote:

 Guys, this is absurd. You finally got the push-to-deploy product 
 right , and now you are discontinuing it. At least pushing source 
 should 
 remain as a feature. 
 The whole appeal of push to deploy was NOT setting up Jenkins. I 
 think you are misjudging the number of people who object to using 
 Jenkins. 
  (By the way

Re: [google-appengine] Re: Push to deploy discontinued?

['Andrew Jessup' via Google App Engine]

=emailutm_source=footer
 .
 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-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-appengine.

 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-appengine/49a123fe-1398-42a3-b7d5-
 b475783ed7fe%40googlegroups.com
 https://groups.google.com/d/msgid/google-appengine/49a123fe-1398-42a3-b7d5-b475783ed7fe%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/83705dd9-df55-44f0-a3fe-7a86a42f32c2%40googlegroups.com
 https://groups.google.com/d/msgid/google-appengine/83705dd9-df55-44f0-a3fe-7a86a42f32c2%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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 http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/c36c62cf-7f09-4216-9faf-a72e6dd2c459%40googlegroups.com
 https://groups.google.com/d/msgid/google-appengine/c36c62cf-7f09-4216-9faf-a72e6dd2c459%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAEF6f2uMyYkwtsS--fND%3DeajnrRRzxWFdpJu2nkBbZjWdKoKcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Python 2 End of Life 2020

['Andrew Jessup' via Google App Engine]

 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 http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/8c465186-d499-4df2-abf4-2551e16060eb%40googlegroups.com
 https://groups.google.com/d/msgid/google-appengine/8c465186-d499-4df2-abf4-2551e16060eb%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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 http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/BCB5BEF3-E37F-4196-A979-9AB066CE1029%40rakkoon.com
 https://groups.google.com/d/msgid/google-appengine/BCB5BEF3-E37F-4196-A979-9AB066CE1029%40rakkoon.com?utm_medium=emailutm_source=footer
 .

 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 http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/CADK-0uiPia5W_H_veOCpUvw9N9heuOeT4BX0hjn%2B9XY3iFsP2g%40mail.gmail.com
 https://groups.google.com/d/msgid/google-appengine/CADK-0uiPia5W_H_veOCpUvw9N9heuOeT4BX0hjn%2B9XY3iFsP2g%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAEF6f2v%2BDJSL89Y4YWcBYVkxozO04KsVjk_3FJ4G7XX-xcCiRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] oAuth 2.0 will become the default authentication mechanism for deploying to App Engine

[Andrew Jessup]

Dear App Engine developers,

In the next release of App Engine you will notice that instead of being 
asked for a username and password, our SDKs will be defaulting to the more 
secure oAuth 2.0 web-based authentication flow to verify your identity. You 
can try this today using the --oauth2 flag with our appfg.py or appcfg.sh 
command line tools.

This change improves the security of your App Engine deployments as the 
oAuth 2.0 authentication flow supports additional Google account security 
features such as 2 Step Authentication 
https://www.google.com/landing/2step/. 

In a subsequent release we will be removing username and password 
authentication entirely.

We expect that most developers will be unaffected by this change, but as 
always we recommend early testing, particularly if you are using continuous 
integration or other tools to authenticate to App Engine. For any issues, 
you can find or ask for help on the Google App Engine Stack Overflow Tag 
http://stackoverflow.com/questions/tagged/google-app-engine, or if you 
have a support package you may open a support ticket 
https://cloud.google.com/support/. 

Happy (and secure) building!

Andrew, on behalf of the Google App Engine team

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/641d5e83-b172-4067-9ec5-2548cb03e982%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] HR datastore is in readonly but there are no errors?

[Andrew Greene]

I am seeing this too.

On Friday, April 10, 2015 at 3:41:49 PM UTC-4, Joshua Smith wrote:

 I’m seeing something, too.

 It appears the entities are being updated but the indexes aren’t.

 That is, I updated a record but I’m not seeing the change. But if I click 
 through to the entity, I do see the change. So basically like what would 
 happen during the “inconsistent” phase of a HR database put. But it’s not 
 getting consistent.

 On Apr 10, 2015, at 3:38 PM, Matija matija@gmail.com javascript: 
 wrote:

 Are we only one with this problem? For the last one hour it is like HR 
 datastore is in some kind read only state but datastore put statements 
 don't return any errors?

 We have noticed that they are testing 1.9.19 java GAE version on some 
 instances.

 Anybody??? What to do? Where to report? Koju posluku porati?

 -- 
 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 javascript:.
 To post to this group, send email to google-a...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-appengine/42a9ecd3-3ee4-4c8b-a64b-d01ab9b519d8%40googlegroups.com
  
 https://groups.google.com/d/msgid/google-appengine/42a9ecd3-3ee4-4c8b-a64b-d01ab9b519d8%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7144a569-46b9-4df2-89b5-36e2e7cfdf14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: HR datastore is in readonly but there are no errors?

[Andrew Greene]

They say they will update me by 13:30 Pacific Time.

On Friday, April 10, 2015 at 4:08:50 PM UTC-4, cloudpre wrote:

 We are also facing same issue for last 30 mins. If there are any updates 
 from Google that anyone has got, please share here.

 On Saturday, April 11, 2015 at 1:08:09 AM UTC+5:30, Matija wrote:

 Are we only one with this problem? For the last one hour it is like HR 
 datastore is in some kind read only state but datastore put statements 
 don't return any errors?

 We have noticed that they are testing 1.9.19 java GAE version on some 
 instances.

 Anybody??? What to do? Where to report? Koju posluku porati?



-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/184803e6-949b-4f11-b4c4-3f8cf8186920%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: HR datastore is in readonly but there are no errors?

[Andrew Greene]

I was just told:

The engineering team believes they have identified the cause of the issue, 
 and are working on remediation now. I will share the status of that when I 
 have news, but no later than 14:00 Pacific Time.


On Friday, April 10, 2015 at 4:27:28 PM UTC-4, Gilberto Torrezan Filho 
wrote:

 I'm having problems with my Datastore as well. I tried to rebuild my index 
 with vacuum_indexes (didn't know it was a general problem) and got:

 Apr 10, 2015 5:17:53 PM 
 com.google.appengine.tools.admin.AbstractServerConnection send1
 WARNING: Error posting to URL: 
 https://appengine.google.com/api/datastore/index/delete?app_id=myid;
 500 Internal Server Error
 htmlheadmeta http-equiv=content-type 
 content=text/html;charset=utf-8title500 Server 
 Error/title/headbody text=#00 bgcolor=#ffh1Error: Server 
 Error/h1h2The server encountered an error and could not complete your 
 request.pPlease try again in 30 seconds./h2h2/h2/body/html
 This is try #0


 On Friday, April 10, 2015 at 4:38:09 PM UTC-3, Matija wrote:

 Are we only one with this problem? For the last one hour it is like HR 
 datastore is in some kind read only state but datastore put statements 
 don't return any errors?

 We have noticed that they are testing 1.9.19 java GAE version on some 
 instances.

 Anybody??? What to do? Where to report? Koju posluku porati?



-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b61ad144-1cd8-4acb-b6eb-5986727f489a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Setting up Unit Test for backend in Android Studio

[Andrew Chen]

Hi guys, 

  this has been plaguing me quite a while. Given i am a new comer to Google 
App Engine with Android Studio. Was wondering if anyone could guide me in 
setting up Test Cases for Backend in Android Studio? 

Thanks. 

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] API for Developers Console?

['Andrew Jessup' via Google App Engine]

Hey Stephen - you're right, these APIs aren't designed with external
consumers in mind (for one thing, they may change without warning as we
make revisions to the console).

If you'd like to know more about our plans for exposing App Engine metrics
and configuration from a stable and more easily consumable endpoint you are
welcome to contact me off-list.

On Tue, Jan 20, 2015 at 4:54 AM, stephanos stephan.beh...@gmail.com wrote:

 Hey there,

 since the rather new Developer Console looks quite feature complete to me
 and appears to be a SPA we would love to make use of REST APIs that expose
 some of its information. In my Chrome Network tab I can see that the app's
 versions are obtained from:
 https://console.developers.google.com/m/gaeconsole/versions?pid=my-project-idmoduleId=default
  -
 but looking at the payload, I suppose this isn't intended for general usage.

 So, how can I obtain the information which version is live, when it was
 deployed and by whom via a REST API call?

 Stephan

 --
 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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/d/optout.




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Far in Future Task Queue ETAs

[Andrew Greene]

Are there any risks/cautions around creating tasks in a push queue with an 
ETA of say 1 month or 1 year or even longer from now?

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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Most active IPs are not listed on Blacklist page

[Andrew Osipenko]

Good afternoon friends,

I am struggling with outgoing bandwidth usage. I think some bots download 
images from my site.
I decided to try embedded appengine IP blocking.

Appengine documentation 
https://developers.google.com/appengine/docs/java/config/dos says:

 Viewing top users in the Administration Console The Administration 
 Console also allows you to view the top users that have recently been 
 hitting your site, ...


 
But if I open my admin page I see no active IP addresses. I see just the 
message:

 No blacklists are defined for this application. 
 You can define blacklists in dos.yaml (Python, PHP and Go) or dos.xml 
 (Java). Learn more about blacklists 
 https://developers.google.com/appengine/kb/general#blacklists. 

https://lh6.googleusercontent.com/-QeKG86SslCo/U5hnYCE9AbI/PSk/bKucKLDIHAU/s1600/gae-blacklist-ip-missing.png


What shall I configure to see the list of active IP addresses? 
 

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cloud Datastore Dashboard not working

[Andrew Chen]

My God. Pre production panic. Same here. This really turns me off.

On Monday, April 28, 2014 10:30:45 AM UTC-4, husayt wrote:

 Is there anybody in google team here, I can address this to?

 Just to recap: I have a major issue with new google develpers console, is 
 that it doesn't load Cloud datastore Query nor Dashboard views. 
 see 
 https://www.dropbox.com/s/5cmgg34z0pw6852/Screenshot%202014-04-28%2015.21.53.png

  I will appreciate if that can be resolved soon, as it is really affecting 
 us.


 On Monday, 21 April 2014 05:15:14 UTC+1, King Royal wrote:

 I have had problems same to you,, Please help me!!



-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: New Pricing

[Andrew Miller]

I would also love to know this too, I have been holding back on some 
development features because of the channel pricing. But if its only quota 
driven now, than that changes a lot for me.

On Wednesday, March 26, 2014 6:07:34 AM UTC-4, Alexis wrote:

 What about Channel API?
 It used to be priced $0.01 / channel opened, but I no longer see it 
 mentioned in the pricing page (neither as bundled or paid service):
 https://cloud.google.com/products/app-engine/



-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[Andrew Jessup]

Hi Igor - actually we do. See Step 2 in under App Engine  Settings 
Custom Domains


On Mon, Apr 14, 2014 at 5:21 AM, Igor Kharin igorkha...@gmail.com wrote:

 Hello Andrew,

 I believe you've mistakenly closed an issue unrelated to this one -- issue
 #777 https://code.google.com/p/googleappengine/issues/detail?id=777.
 I've checked the new UI and it doesn't seem like you guys support naked
 domains just yet.


 On Sat, Apr 12, 2014 at 6:31 AM, Andrew Jessup jes...@google.com wrote:

 Hi Everyone,

 I'm happy to report that we have just added support for mapping custom
 domains to an App Engine application directly from within the Google
 Developers Console (https://console.developers.google.com/). This means
 that you can associate your domains without being required to purchase
 Google Apps for each domain first.

 This isn't dependent on our recently released Cloud DNS service -
 although if you *are* looking for a great DNS, they do go well together
 :)

 There are still some features we're looking to add to this - notably,
 support for SSL for custom domains (which is still available if you use
 Google Apps to associate a domain, and is available automattically from
 your *.appspot.com URLs). In the meantime, we hope you find this to be a
 more effective and simpler way to set up your App Engine apps.

 Since Google Apps is no longer necessary, from today we are no longer
 offering the Jump Start credit to new applicants. Those who have already
 been awarded the credit will still be able to draw down from any unused
 credit on their account, and if you have recently applied prior to today
 then we will still review your application. However new applications will
 not be accepted.

 Thanks for your patience.

 Regards,

 Andrew
 Product Manager, Google Cloud Platform

 On Thursday, 27 March 2014 20:39:24 UTC+1, Vinny P wrote:

 On Thu, Mar 27, 2014 at 2:26 PM, Barry Hunter barryb...@gmail.com
  wrote:

 Can't just use cloud-dns to CNAME your domain to ghs.googlehosted.com -
 *without *using Google Apps, because still needs to know the
 domain-to-appid mapping.

 So can use Cloud-DNS, but still need Google Apps *too*.



 I agree with Barry. I read through the Cloud DNS documentation, but
 unless I missed something, I don't see a way to associate domains with
 specific applications.

 For instance, I can create a managed zone and associate it with a
 project by calling this REST command: https://developers.google.com/
 cloud-dns/api/v1beta1/managedZones/create . But where is the
 association between domain/project to App Engine ID?


 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
 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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/d/optout.




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[Andrew Jessup]

Hey PK - we definitely realise that SSL is important. Knowing how critical
it is to support custom domains without Google Apps though, we wanted to
release support for that first rather than have everyone wait until SSL was
ready.


On Sun, Apr 13, 2014 at 7:27 PM, PK p...@gae123.com wrote:

 Hi Andrew,

 This is a great step in the right direction. However, SSL is required for
 a very big class of applications these days. I would have expected Google
 waited to declare victory (and close the issue like you did etc) when SSL
 support is there as well. In any case, I hope SSL support is coming soon.

 PK
 www.gae123.com

 On Apr 11, 2014, at 4:31 PM, Andrew Jessup jes...@google.com wrote:

 Hi Everyone,

 I'm happy to report that we have just added support for mapping custom
 domains to an App Engine application directly from within the Google
 Developers Console (https://console.developers.google.com/). This means
 that you can associate your domains without being required to purchase
 Google Apps for each domain first.

 This isn't dependent on our recently released Cloud DNS service - although
 if you *are* looking for a great DNS, they do go well together :)

 There are still some features we're looking to add to this - notably,
 support for SSL for custom domains (which is still available if you use
 Google Apps to associate a domain, and is available automattically from
 your *.appspot.com URLs). In the meantime, we hope you find this to be a
 more effective and simpler way to set up your App Engine apps.

 Since Google Apps is no longer necessary, from today we are no longer
 offering the Jump Start credit to new applicants. Those who have already
 been awarded the credit will still be able to draw down from any unused
 credit on their account, and if you have recently applied prior to today
 then we will still review your application. However new applications will
 not be accepted.

 Thanks for your patience.

 Regards,

 Andrew
 Product Manager, Google Cloud Platform

 On Thursday, 27 March 2014 20:39:24 UTC+1, Vinny P wrote:

 On Thu, Mar 27, 2014 at 2:26 PM, Barry Hunter barryb...@gmail.com
  wrote:

 Can't just use cloud-dns to CNAME your domain to ghs.googlehosted.com -
 *without *using Google Apps, because still needs to know the
 domain-to-appid mapping.

 So can use Cloud-DNS, but still need Google Apps *too*.



 I agree with Barry. I read through the Cloud DNS documentation, but
 unless I missed something, I don't see a way to associate domains with
 specific applications.

 For instance, I can create a managed zone and associate it with a project
 by calling this REST command: https://developers.google.com/
 cloud-dns/api/v1beta1/managedZones/create . But where is the association
 between domain/project to App Engine ID?


 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
 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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/d/optout.




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[Andrew Jessup]

Hi Everyone,

I'm happy to report that we have just added support for mapping custom 
domains to an App Engine application directly from within the Google 
Developers Console (https://console.developers.google.com/). This means 
that you can associate your domains without being required to purchase 
Google Apps for each domain first.

This isn't dependent on our recently released Cloud DNS service - although 
if you *are* looking for a great DNS, they do go well together :)

There are still some features we're looking to add to this - notably, 
support for SSL for custom domains (which is still available if you use 
Google Apps to associate a domain, and is available automattically from 
your *.appspot.com URLs). In the meantime, we hope you find this to be a 
more effective and simpler way to set up your App Engine apps.

Since Google Apps is no longer necessary, from today we are no longer 
offering the Jump Start credit to new applicants. Those who have already 
been awarded the credit will still be able to draw down from any unused 
credit on their account, and if you have recently applied prior to today 
then we will still review your application. However new applications will 
not be accepted.

Thanks for your patience.

Regards,

Andrew
Product Manager, Google Cloud Platform

On Thursday, 27 March 2014 20:39:24 UTC+1, Vinny P wrote:

 On Thu, Mar 27, 2014 at 2:26 PM, Barry Hunter 
 barryb...@gmail.comjavascript:
  wrote:

 Can't just use cloud-dns to CNAME your domain to ghs.googlehosted.com - 
 *without *using Google Apps, because still needs to know the 
 domain-to-appid mapping. 

 So can use Cloud-DNS, but still need Google Apps *too*. 



 I agree with Barry. I read through the Cloud DNS documentation, but unless 
 I missed something, I don't see a way to associate domains with specific 
 applications. 

 For instance, I can create a managed zone and associate it with a project 
 by calling this REST command: 
 https://developers.google.com/cloud-dns/api/v1beta1/managedZones/create . 
 But where is the association between domain/project to App Engine ID?
   
  
 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine 1.9.2 Released

[Andrew Jessup]

We've got some good things coming folks, some long requested features for
Java in the pipeline.
On Apr 10, 2014 12:38 PM, Vinny P vinny...@gmail.com wrote:

 On Tue, Apr 8, 2014 at 9:59 AM, Andrew Jessup jes...@google.com wrote:

 We are pleased to announce the latest release of Google App Engine 1.9.2, 
 which has now been rolled out to all applications. Release 1.9.2 includes 
 the following enhancements.PHP==



  As a Java coder, I'm disappointed to see no new Java love in this patch.
 But that's OK, I'm used to disappointment: It's like my prom night all over
 again


 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine 1.9.2 Released

[Andrew Jessup]

Hi Everyone,
We are pleased to announce the latest release of Google App Engine 1.9.2, which 
has now been rolled out to all applications. 
Release 1.9.2 includes the following enhancements.
All languages==- We are pleased to announce the 
availability of Dedicated Memcache service  to our customers in the 
EU.PHP==- Users now have the ability to embed 
images in emails via the Content-Id  attachment header.
https://code.google.com/p/googleappengine/issues/detail?id=965 
https://www.google.com/url?q=https://code.google.com/p/googleappengine/issues/detail%3Fid%3D965usg=AFQjCNHNf4SDA522hNIBjpvOQnJBcViTQA-
 The Zip module is now included in the SDK.
https://code.google.com/p/googleappengine/issues/detail?id=10703 
https://www.google.com/url?q=https://code.google.com/p/googleappengine/issues/detail%3Fid%3D10703usg=AFQjCNFME_uvL07mZlWBrip0ykyhB7D99Q-
 Fixed an issue with the Google Cloud Storage upload proxy truncating POST  
field data when it is longer than 80 characters.
https://code.google.com/p/googleappengine/issues/detail?id=10355 
https://www.google.com/url?q=https://code.google.com/p/googleappengine/issues/detail%3Fid%3D10355usg=AFQjCNFXqiSBMyctMpq9MgMVjwRPsj9DqQ-
 Fixed an issue with default max sized uploads no longer handling unlimited  
size uploads.
https://code.google.com/p/googleappengine/issues/detail?id=10727 
https://www.google.com/url?q=https://code.google.com/p/googleappengine/issues/detail%3Fid%3D10727usg=AFQjCNHVAnn2nCChZecikBYTGC-vI63orQ
Kind regards,
Andrew JessupProduct Manager, Google Cloud Platform

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Is GAE memcache API thrad-safe?

[Andrew Miller]

You want to look into 
memcache.cas() 
https://developers.google.com/appengine/docs/python/memcache/clientclass#Client_cas

On Thursday, March 13, 2014 11:41:54 PM UTC-4, Chen Ym wrote:

 Shoud I use a lock to protect the memcached object?


-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Best way to delete data by time (NDB) (Python)

[Andrew Miller]

What is the most cost efficient way to delete data from NDB that is x days 
old?

For example, if you only wanted to store chat logs or something for only 30 
days. 

Would you run a backend once a day to query for any entity that is less 
than x time?

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google App Engine / Cloud Storage Uploads for php broken in 1.9.0?

[Andrew Jessup]

Hi David - this is a known issue, we expect to get it addressed ASAP.
https://code.google.com/p/googleappengine/issues/detail?id=10634

And you're quite right - a bug like this should never make it to
production.

Right now we're auditing exactly how an issue like was able to be shipped,
and updating our pre-release testing framework includes checks for
regressions like this.


On Wed, Feb 26, 2014 at 12:55 PM, David Tyler the.david.ty...@gmail.comwrote:

 Has anyone else noticed a problem uploading files to GCS using the php
 libraries in 1.9.0?

 My production app has been on 1.8.9 for weeks, and today was automatically
 upgraded to 1.9.0.

 Ever since, I get a php error coming from Google's runtime:

 strpos(): Empty needle
 /base/data/home/runtimes/php/sdk/google/appengine/ext/cloud_storage_streams/CloudStorageStreamWrapper.php
 line 168

 I found a stack overflow post, looks like someone using the 1.9.0 beta had
 this problem earlier this month:

 http://stackoverflow.com/questions/21545873/google-cloud-storage-error-on-upload-strpos-empty-needle

 Is there any official word on this bug or release?
 Seems really odd to me that this slipped through and was automatically
 pushed to production apps.

 --
 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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/d/optout.




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[Andrew Jessup]

Hi Folks,

I don't have a more concrete update to share at this time, since we don't
like talking about features that haven't been released yet.

But we completely aware this is a huge pain point, and engineers *are* actively
working on it right now.


On Wed, Feb 26, 2014 at 4:07 AM, Max Völkel max.at.xam...@gmail.com wrote:

 Such  a great product sleeping in such an unusable state. Don't your
 analytics clearly show a decline in new users?

 --
 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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] A comparison between Digital Ocean $5 plan and App Engine B$ instance type.

[Andrew Mackenzie]

Good post Barry. Things are not so simple. How much salary for Ops guys to keep 
that thing running 24x7?

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] This is an important note for anyone still deploying Java 6 applications on Google App Engine

[Andrew Jessup]

Hi Everyone,

This is an important note for anyone still deploying Java 6 applications on 
Google App Engine.

As part of our previously announced 
planhttps://groups.google.com/forum/#!topic/google-appengine/xxXd6NftS1Qto 
fully upgrade App Engine to Java 7 - from the next release App Engine 
will no longer allow applications to be deployed as Java 6. Running Java 6 
applications will continue to run, and you can deploy your application as 
Java 7.

Java 7 is backwards compatible with Java 6, as well as providing a number 
of benefits to developers. Please refer to the Oracle white paper on Java 7 
and Java 6 compatibility for additional 
details: http://www.oracle.com/technetwork/java/javase/compatibility-417013.html


*How do I know if I am still deploying Java 6 code?*
You can see if your app is running in Java 6 or Java 7 from the Versions 
section of the App Engine Admin console.

If you are using a version of the App Engine for Java SDK later than 1.7.8, 
and you are not explicitly deploying to Java 6 using the --with_java6 flag, 
then you are already deploying Java 7 code.


*How do I deploy my app as Java 7?*
Update your SDK to a recent version (1.7.8 or higher), and deploy your app 
(and make sure you’re not using the --with_java6 flag). We recommend 
deploying your to a non-default version first to double check that 
everything works as expected.

If you still absolutely need to deploy Java 6 applications, you may request 
a temporary exemption from this policy for your application from this 
form:http://goo.gl/ycffXq. 
We will only accept exceptions for applications that are (a) are Premier or 
have billing enabled, and (b) have a provably demonstrated compatibility 
problems running their application with Java 7. Please also note that it 
may take us a couple of days to process your application.

We’ve worked hard to make this upgrade process as transparent as possible. 
Today, thousands of Java 6 applications on Google App Engine already have 
migrated successfully to Java 7, and for the vast majority the upgrade has 
been entirely transparent and required no changes to code.

If you have any questions about our Java 6 to Java 7 upgrade, you can reach 
us at google-appengine-java-6-to-7-migrat...@googlegroups.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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Google Apps No Longer Free

[Andrew Jessup]

Hi James,

The $50 credit is for spend on Google App Engine. Unfortunately due to the 
way App Engine charges are currently presented, the credit doesn't appear 
in your statement, but rather will appear as a deduction against the first 
$50 of your spend on App Engine.

On Tuesday, 5 November 2013 09:54:20 UTC-8, James Gilliam wrote:

 Just got a response from google apps about the $50 credit ... they say it 
 doesn't apply to google apps ...

 Andrew responded with 

 I see. Unfortunately this credit is only available for the first $50 of 
 your Google App Engine spend, not Google Apps. 

 I can't see where the credit was applied anywhere ... and don't even 
 understand what Andrew is talking about ...

 Wasn't the credit suppose to be for the google apps account  
 because of the charge for using the damn thing even if you don't want the 
 email?

 On Thursday, December 6, 2012 6:42:42 PM UTC-8, Greg wrote:

 Just saw that Google Apps is no longer free for 
 businesseshttp://googleenterprise.blogspot.co.nz/2012/12/changes-to-google-apps-for-businesses.html
 . 

 I have no problem paying for a Google Apps account where I actually use 
 Google apps, but at the moment you have to have a Google Apps account to 
 link a domain to an Appengine app. Some of our apps have two or three 
 domains showing the same app, and because you need to have an account for 
 each email address that Appengine sends email from, we have three or four 
 accounts per domain. So this is potentially going to add $600 per year to 
 our costs - all for virtual accounts that don't actually use Google Apps at 
 all.

 Can someone from Google comment please? Either Google Apps accounts need 
 to remain free if they are associated with Appengine apps, or there needs 
 to be another way to link domains (and authorise email addresses) for 
 Appengine.




-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: how to start all modules instances on dev server?

[Andrew Jessup]

Tapir, was the bad character in the App Engine documentation somewhere? If 
so, where?

On Sunday, 5 January 2014 00:33:33 UTC-8, Tapir wrote:

 Ok, found the problem by accident.

 After finding the google maven example on github works well, I copied the 
 META-INF folder to my project.
 A replace files dialog was expected to show up.
 But, no, it didn't show!
 Then there are two META-INF folders in my project.
 Two identical folders in my project!!!

 Researched it for a while, I copy the two folder name into a notepad file, 
 the difference is obvious.
 One - character is longer than the other one.
  (But in windows file explorer, they are the same length! However, in IE 
 browser,  the shorter one becomes longer)
 The hexdump shows the longer is e22d 9180, the shorter one is 000A.

 Ok, the short one is the correct one. It is META-INF
 The longer one is META-INF.

 So, it looks it must be my mistake?
 Aha, no.
 I search the longer one in the google document: 
 https://developers.google.com/appengine/docs/java/modules/
 Eh, it seems this page mixes the longer one and the shorter one many times.
 I'm so lucky that I picked the wrong one.

 Can't believe no one else has found this problem before. 
 Does this mean there are very few projects using the modules feature?




 On Thursday, January 2, 2014 5:31:01 PM UTC+8, Tapir wrote:



 On Thursday, January 2, 2014 3:31:14 PM UTC+8, Vinny P wrote:

 On Wed, Jan 1, 2014 at 11:03 PM, Tapir tapi...@gmail.com wrote:

 This page mentions all modules instances will be started. 
 https://developers.google.com/appengine/docs/java/modules/routing
 But I don't how to do this. When call dev_server on a second module, it 
 says:
 Could not open the requested socket: Address already in use: bind. Try 
 overriding --address and/or --port.




 The dev server should be starting up all the modules automatically, you 
 don't need to call the dev server a second time.

 When you call the dev server on the second module - after already 
 calling it on the first module - the second dev server instance is unable 
 to run because (as it points out in the error text) the first dev server 
 instance is already bound to the port. So this is correct behavior.


 On Wed, Jan 1, 2014 at 11:03 PM, Tapir tapi...@gmail.com wrote:

 If I call dev_server on the ear directory, it says

 com.google.apphosting.utils.config.AppEngineConfigException: Could not 
 locate D:\my-project\ear\WEB-INF\appengine-web.xml

 yes, there is no WEB-INF in the ear folder but only a META-INF folder 
 and module folders in the ear folder.




 More than likely, the dev server is interpreting your folder as a basic, 
 single-module application rather than a multi-module application (i.e. JAR 
 rather than an EAR). Can you post the stack trace for the 
 AppEngineConfigException?


 yes, I think so. How to let dev_server not interpret the folder as a 
 single-module app?

 The folder structure is like this:
 my-project
 --- ear
 -- META-INF
 - appengine-application.xml
 - application.xml
 -- default
 - war
  WEB-INF
 --- appengine-web.xml
  web.xml
 -- websockets
 - war
  WEB-INF
 --- appengine-web.xml
  web.xml

 The following is added in application.xml:

   module
 web
   web-uridefault/web-uri
   context-rootdefault/context-root
 /web
   /module
   module
 web
   web-uriwebsokets/web-uri
   context-rootwebsokets/context-root
 /web
   /module

 I downloaded the example on git, but I dislike the mvn style so I give up 
 it.
 The mvn style hide too many details, so I think it is not a good example 
 to start.

 Afte run dev_appserver.cmd ear, the stack trace is output:

 Jan 02, 2014 5:15:46 PM 
 com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
 SEVERE: Received exception processing 
 D:\my-project\ear\WEB-INF/appengine-web.xml
 com.google.apphosting.utils.config.AppEngineConfigException: Could not 
 locate D:\my-project\ear\WEB-INF\appengine-web.xml
 at 
 com.google.apphosting.utils.config.AppEngineWebXmlReader.getInputStream(AppEngineWebXmlReader.java:140)
 at 
 com.google.apphosting.utils.config.AppEngineWebXmlReader.readAppEngineWebXml(AppEngineWebXmlReader.java:75)
 at 
 com.google.apphosting.utils.config.EarHelper.readWebModule(EarHelper.java:166)
 at 
 com.google.appengine.tools.development.ApplicationConfigurationManager$WarModuleConfigurationHandle.readConfiguration(ApplicationConfigurationManager.java:399)
 at 
 com.google.appengine.tools.development.ApplicationConfigurationManager.init(ApplicationConfigurationManager.java:146)
 at 
 com.google.appengine.tools.development.ApplicationConfigurationManager.newWarConfigurationManager(ApplicationConfigurationManager.java:88)
 at 
 com.google.appengine.tools.development.DevAppServerImpl.init(DevAppServerImpl.java:139)
 

Re: [google-appengine] Re: Google App Engine remote_api returns 404 using remote_api_shell.py

[Andrew Free]

Try uploading/deploying your code sometimes it just needs to be pushed to 
google. I’m not sure how I ended up solving this exactly. I have had lots of 
issues with the remote API. 


On Dec 16, 2013, at 6:41 AM, Ying Ding yd...@corp.lawyer.com wrote:

 I ran into this problem today too. Have you solved your problem?  Hope you 
 can see this and drop a line about your solution. Thank you!
 
 On Friday, September 6, 2013 1:12:02 AM UTC-4, Andrew Free wrote:
 I'm using googles built in tool for connecting to the remote api so I don't 
 even have info in my client or app.yaml I could change. I have no idea why I 
 suddenly cant connect.
 
 My friend who is also working on the project with me tried on his machine and 
 got the same error. It was working fine for the past couple months. I'm also 
 using the remote_api_shell so it can't be something in my code?
 
 My app.yaml has
 
 builtins:
 
 - remote_api: on
 
 
 
 [ rever ~/Documents/buybottmerge/buybott-gae ] remote_api_shell.py -s 
 myappname.appspot.com
 Traceback (most recent call last):
   File /usr/local/bin/remote_api_shell.py, line 171, in module
 run_file(__file__, globals())
   File /usr/local/bin/remote_api_shell.py, line 167, in run_file
 execfile(script_path, globals_)
   File 
 /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/remote_api_shell.py,
  line 152, in module
 main(sys.argv)
   File 
 /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/remote_api_shell.py,
  line 148, in main
 appengine_rpc.HttpRpcServer)
   File 
 /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/remote_api_shell.py,
  line 76, in remote_api_shell
 rpc_server_factory=rpc_server_factory)
   File 
 /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py,
  line 725, in ConfigureRemoteApi
 app_id = GetRemoteAppIdFromServer(server, path, rtok)
   File 
 /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py,
  line 568, in GetRemoteAppIdFromServer
 response = server.Send(path, payload=None, **urlargs)
   File 
 /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/appengine_rpc.py,
  line 393, in Send
 f = self.opener.open(req)
   File 
 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py,
  line 400, in open
 response = meth(req, response)
   File 
 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py,
  line 513, in http_response
 'http', request, response, code, msg, hdrs)
   File 
 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py,
  line 438, in error
 return self._call_chain(*args)
   File 
 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py,
  line 372, in _call_chain
 result = func(*args)
   File 
 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py,
  line 521, in http_error_default
 raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
 urllib2.HTTPError: HTTP Error 404: Not Found
 I can see the errors on my logs in the dashboard as well. So something is 
 working well enough for it to get that far before failing.
 
 2013-09-05 18:13:35.735 /_ah/remote_api?rtok=569217424211 404 4ms 0kb 
 Google-remote_api/1.0 Darwin/12.4.0 Python/2.7.2.final.0 gzip
 
 50.53.136.79 - - [05/Sep/2013:18:13:35 -0700] GET 
 /_ah/remote_api?rtok=569217424211   HTTP/1.1 404 130 - 
 Google-remote_api/1.0 Darwin/12.4.0 Python/2.7.2.final.0 gzip   
 myappname.appspot.com ms=4 cpu_ms=0 cpm_usd=0.15 
 app_engine_release=1.8.4   instance=00c61b117cbd87090d90186a5635840f196c4d14
 
 
 -- 
 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/t7L4URlUr0A/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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/groups/opt_out.

-- 
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

Re: [google-appengine] Blank page on PHP Hello World

[Andrew Jessup]

You need to specify the php-cgi binary, not the PHP binary

On Tuesday, 10 December 2013 20:02:33 UTC-8, Vinny P wrote:

 On Fri, Dec 6, 2013 at 7:10 PM, Jefrey Sobreira 
 jefrey@gmail.comjavascript:
  wrote:

 *The path specified with the --php_executable_path flag () does not 
 exist.* 

 So I changed the command line to:
 python dev_appserver.py helloworld/ --php_executable_path /usr/bin/php
 (i tired as root and also as non-root)
 Now that error isn't appearing anymore. But all I see is a blank page...



 Can you run a search for the PHP executable (i.e. *run sudo find / -name 
 php-cgi* )? I was under the impression that PHP installs under 
 *usr/bin/php-cgi*.
   
  
 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Wait, what? App Engine doesn't work with latest version of WordPress?

[Andrew Jessup]

Has anyone been able to reproduce this problem? A couple of folks on the 
team tried installing the latest WordPress using our tutorial and it seemed 
to work well.

If anyone can reproduce it, it would be great if they could file a bug - 
including the exact steps here - 
https://code.google.com/p/googleappengine/issues/list

On Saturday, 30 November 2013 15:58:41 UTC-8, timh wrote:

 Except they can't automatically start upgrading wordpress on appengine.  
 The only way to update code is via deploying a new version.



 On Saturday, November 30, 2013 11:47:58 PM UTC+8, OC2PS wrote:

 Looks like App Engine has trouble with WordPress 3.7.1 
 http://wordpress.org/support/topic/trouble-running-local-wordpress-in-google-app-engine

 This is terrible especially as WordPress have decided that they will 
 start automatically updating WordPress without human intervention!



-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Google App Engine remote_api returns 404 using remote_api_shell.py

[Andrew Free]

I use the deploy built into that app engine launcher that comes with the 
SDK on osx. I don't know if that is the same thing. I read about doing a 
normal appcfg update to fix this but it doesn't seem to be the problem for 
me. 


On Friday, October 18, 2013 8:03:13 AM UTC-7, gumptionthomas wrote:

 I know this is a little late, but are you using the git-push-to-deploy 
 feature on your app?

 I've found that the builtins defined in app.yaml do not work after a 
 push-to-deploy (they return 404s) but doing a normal appcfg update makes 
 them work again.

 I experienced these 404 failures after push-deploys with both remote_api 
 and deferred.


-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.