[google-appengine] Please explain project VS application - service - version - instance

[Karoly Kantor]

I am somewhat confused about the nomenclature. Can someone maybe explain?

On this 
page: 
https://cloud.google.com/appengine/docs/standard/python/an-overview-of-app-engine
there is a description of the hierarchy of what application - service - 
version - instance mean.

But everything i have is in a "project". How is a "project" related to the 
application - service - version - instance structure?
Is one project = one application?

I see no option to create an "application", what I can create is a 
"project".

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/fbafcf51-2c18-4dcc-bb28-eb2730ac065c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Hosting de pago

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

Hello Adrian, 

A deployed app engine service would scale up to accommodate increased 
bandwidth. More capacity would automatically get added as workloads 
increase, which amounts to illimited bandwidth, in practical terms, exactly 
as you say. You can find relevant information in the "Designing for Scale" 
document . If the 
free quotas are exceeded, you get charged for the extra usage, as detailed 
on the "Quotas" page . 


You can choose a domain of your choice and use it in place of the default 
.appspot domain. More detail and further links in the "Using Custom Domains 
and SSL" online document 

. 

-- 
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/c6574382-cf5f-48c5-a683-1895b75328a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: does google appengine have suggested solution to use letsencrypt certs?

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

Our engineering team is working on this functionality, and you can follow 
along with their progress on the Public Issue Tracker 
. As stated in the tracker 
, you can currently 
use the Admin API 

 to 
update certs in the meantime. 

-- 
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/fe1c660f-8ebe-44ac-83b3-4c679390ef17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Please explain project VS application - service - version - instance

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

Your Google Cloud Platform project 
 is 
a basic unit of organization to which every Google Cloud Platform service 
is attached to.

Each project can choose to enable any of the platform's features, including 
App Engine. This lets a project have up to one application. To enable App 
Engine on your project, simply visit 
https://console.cloud.google.com/appengine. Your application can consist of up 
to 20 

 services. 

Each service 

 
is accessed through a different URL and while services can share many of 
App Engine's features at the application level, they are entirely 
independent from one another. Note that by default App Engine will use the 
"default" service for everything, so you don't have to care about services 
until you want to. Each service can have up to 120 

versions.

Versions are versions of a specific service. They hold the actual code with 
which the application functions. Versions of the same service can be in any 
language you want and even perform entirely different functions. You get to 
choose which version(s) you want to be used for serving traffic to your 
application. 

Finally instances are the actual servers answering requests made to your 
application. They are created using the code of the currently active 
version(s). Versions can have as many active instances as is required to 
serve their traffic. How many instances you have can have active can be 
configured 
in app.yaml 

.

This is a fairly basic explanation of course, tell us if there's parts of 
it you have a problem with.

On Monday, June 19, 2017 at 8:26:17 AM UTC-4, Karoly Kantor wrote:
>
> I am somewhat confused about the nomenclature. Can someone maybe explain?
>
> On this page: 
> https://cloud.google.com/appengine/docs/standard/python/an-overview-of-app-engine
> there is a description of the hierarchy of what application - service - 
> version - instance mean.
>
> But everything i have is in a "project". How is a "project" related to the 
> application - service - version - instance structure?
> Is one project = one application?
>
> I see no option to create an "application", what I can create is a 
> "project".
>
> 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/6db35273-bbc7-4bfc-9277-98180cb0895f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Please explain project VS application - service - version - instance

[Karoly Kantor]

Thank you. "This lets a project have up to one application" was the key 
message to me.

Some more questions for total clarity:

1. So when I upload my application, the "application: " part of 
app.yaml should be the project name, is that right? if not, what is the 
application name in app.yaml used for?

2. Do services always share a datastore name space, i.e. do entities of the 
same name referenced in different services always refer to the same data?



On Monday, June 19, 2017 at 5:04:38 PM UTC+2, Yannick (Cloud Platform 
Support) wrote:
>
> Your Google Cloud Platform project 
>  
> is 
> a basic unit of organization to which every Google Cloud Platform service 
> is attached to.
>
> Each project can choose to enable any of the platform's features, 
> including App Engine. This lets a project have up to one application. To 
> enable App Engine on your project, simply visit 
> https://console.cloud.google.com/appengine. Your application can consist 
> of up to 20 
> 
>  services. 
>
> Each service 
> 
>  
> is accessed through a different URL and while services can share many of 
> App Engine's features at the application level, they are entirely 
> independent from one another. Note that by default App Engine will use the 
> "default" service for everything, so you don't have to care about services 
> until you want to. Each service can have up to 120 
> 
> versions.
>
> Versions are versions of a specific service. They hold the actual code 
> with which the application functions. Versions of the same service can be 
> in any language you want and even perform entirely different functions. You 
> get to choose which version(s) you want to be used for serving traffic to 
> your application. 
>
> Finally instances are the actual servers answering requests made to your 
> application. They are created using the code of the currently active 
> version(s). Versions can have as many active instances as is required to 
> serve their traffic. How many instances you have can have active can be 
> configured 
> in app.yaml 
> 
> .
>
> This is a fairly basic explanation of course, tell us if there's parts of 
> it you have a problem with.
>
> On Monday, June 19, 2017 at 8:26:17 AM UTC-4, Karoly Kantor wrote:
>>
>> I am somewhat confused about the nomenclature. Can someone maybe explain?
>>
>> On this page: 
>> https://cloud.google.com/appengine/docs/standard/python/an-overview-of-app-engine
>> there is a description of the hierarchy of what application - service - 
>> version - instance mean.
>>
>> But everything i have is in a "project". How is a "project" related to 
>> the application - service - version - instance structure?
>> Is one project = one application?
>>
>> I see no option to create an "application", what I can create is a 
>> "project".
>>
>> 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/41fc35b4-15fe-4bdd-9407-1749a5737c8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Please explain project VS application - service - version - instance

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

I'm glad I was able to clear that up for you, here's the answer to your 
follow-up questions:

1. That is correct, though that particular parameter might not be necessary 
depending
 
on the way you are deploying your application. The app.yaml reference 
 has a 
pretty good explanation of each element that can go into it.

2. All services of your application use the default Datastore namespace unless 
you tell them otherwise 
.

On Monday, June 19, 2017 at 11:17:47 AM UTC-4, Karoly Kantor wrote:
>
> Thank you. "This lets a project have up to one application" was the key 
> message to me.
>
> Some more questions for total clarity:
>
> 1. So when I upload my application, the "application: " part of 
> app.yaml should be the project name, is that right? if not, what is the 
> application name in app.yaml used for?
>
> 2. Do services always share a datastore name space, i.e. do entities of 
> the same name referenced in different services always refer to the same 
> data?
>
>
>
> On Monday, June 19, 2017 at 5:04:38 PM UTC+2, Yannick (Cloud Platform 
> Support) wrote:
>>
>> Your Google Cloud Platform project 
>>  
>> is 
>> a basic unit of organization to which every Google Cloud Platform service 
>> is attached to.
>>
>> Each project can choose to enable any of the platform's features, 
>> including App Engine. This lets a project have up to one application. To 
>> enable App Engine on your project, simply visit 
>> https://console.cloud.google.com/appengine. Your application can consist 
>> of up to 20 
>> 
>>  services. 
>>
>> Each service 
>> 
>>  
>> is accessed through a different URL and while services can share many of 
>> App Engine's features at the application level, they are entirely 
>> independent from one another. Note that by default App Engine will use the 
>> "default" service for everything, so you don't have to care about services 
>> until you want to. Each service can have up to 120 
>> 
>> versions.
>>
>> Versions are versions of a specific service. They hold the actual code 
>> with which the application functions. Versions of the same service can be 
>> in any language you want and even perform entirely different functions. You 
>> get to choose which version(s) you want to be used for serving traffic to 
>> your application. 
>>
>> Finally instances are the actual servers answering requests made to your 
>> application. They are created using the code of the currently active 
>> version(s). Versions can have as many active instances as is required to 
>> serve their traffic. How many instances you have can have active can be 
>> configured 
>> in app.yaml 
>> 
>> .
>>
>> This is a fairly basic explanation of course, tell us if there's parts of 
>> it you have a problem with.
>>
>> On Monday, June 19, 2017 at 8:26:17 AM UTC-4, Karoly Kantor wrote:
>>>
>>> I am somewhat confused about the nomenclature. Can someone maybe explain?
>>>
>>> On this page: 
>>> https://cloud.google.com/appengine/docs/standard/python/an-overview-of-app-engine
>>> there is a description of the hierarchy of what application - service - 
>>> version - instance mean.
>>>
>>> But everything i have is in a "project". How is a "project" related to 
>>> the application - service - version - instance structure?
>>> Is one project = one application?
>>>
>>> I see no option to create an "application", what I can create is a 
>>> "project".
>>>
>>> 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/768c30ad-4dda-4e74-8e91-0ca7e363e74f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dotnet CLI version on Google Cloud Shell

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

Hello Vicente,

Changes made to your Cloud Shell outside of its home directory will not 
persist between invocations of the Cloud Shell, so there is no way you can 
update the installed version of the dotnet cli yourself. What you could do 
at the moment is install the latest version of the dotnet cli on a GCE 
f1-micro instance, which is included in the GCE Always Free Usage Limits 
.

To get support for other versions of dotnet on the Cloud Shell, you should 
create 
a Feature Request 
 on 
the Cloud Shell's issue tracker.

On Sunday, June 18, 2017 at 12:22:39 PM UTC-4, Vicente Maciel Junior wrote:
>
> Hi people,
>
> I'm trying to implemented a way to build and publish apps to the App 
> Engine Flex using the Google Cloud Shell.
> So, the idea is to be able to:
>
> 1 - Access the Google Cloud Console
> 2 - Open the Google Cloud Shell
> 3 - Clone/pull my source code from the Google Source Repository
> 4 - Compile it (dotnet publish -c Release)
> 5 - Publish the updated version to the cloud using: gcloud beta app deploy 
> 
>
> Nothing new at this point...
>
> The problem starts when I try to do the same with apps built to use dotnet 
> core 1.0.x greater than 1.0.0, because the Google Cloud Shell has the 
> dotnet CLI at version 1.0.0...
>
> So my question is: Is there a way to update the dotnet CLI to 1.0.x or any 
> other suggested way to have success with this process?
>
> My objective with this approach is to eliminate the process of create the 
> image on my machine and upload it consuming time because of the upload of 
> the image.
>
> Being able to code, test, debug on my machine and then commit and push the 
> modifications to the cloud to update the image at the Google Cloud, may be 
> a much faster way, I believe.
>
> Thanks for any help, comment and/or suggestion.
>
> Vicente Maciel Jr
>

-- 
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/cd5d7a76-fc9f-4968-a6e6-a087818a40c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dotnet CLI version on Google Cloud Shell

[Vicente Maciel Junior]

Thank you so much for the info!

I'll submit this request.

Regards

Em segunda-feira, 19 de junho de 2017 13:31:10 UTC-3, Yannick (Cloud 
Platform Support) escreveu:
>
> Hello Vicente,
>
> Changes made to your Cloud Shell outside of its home directory will not 
> persist between invocations of the Cloud Shell, so there is no way you can 
> update the installed version of the dotnet cli yourself. What you could do 
> at the moment is install the latest version of the dotnet cli on a GCE 
> f1-micro instance, which is included in the GCE Always Free Usage Limits 
> .
>
> To get support for other versions of dotnet on the Cloud Shell, you should 
> create 
> a Feature Request 
>  on 
> the Cloud Shell's issue tracker.
>
> On Sunday, June 18, 2017 at 12:22:39 PM UTC-4, Vicente Maciel Junior wrote:
>>
>> Hi people,
>>
>> I'm trying to implemented a way to build and publish apps to the App 
>> Engine Flex using the Google Cloud Shell.
>> So, the idea is to be able to:
>>
>> 1 - Access the Google Cloud Console
>> 2 - Open the Google Cloud Shell
>> 3 - Clone/pull my source code from the Google Source Repository
>> 4 - Compile it (dotnet publish -c Release)
>> 5 - Publish the updated version to the cloud using: gcloud beta app 
>> deploy 
>>
>> Nothing new at this point...
>>
>> The problem starts when I try to do the same with apps built to use 
>> dotnet core 1.0.x greater than 1.0.0, because the Google Cloud Shell has 
>> the dotnet CLI at version 1.0.0...
>>
>> So my question is: Is there a way to update the dotnet CLI to 1.0.x or 
>> any other suggested way to have success with this process?
>>
>> My objective with this approach is to eliminate the process of create the 
>> image on my machine and upload it consuming time because of the upload of 
>> the image.
>>
>> Being able to code, test, debug on my machine and then commit and push 
>> the modifications to the cloud to update the image at the Google Cloud, may 
>> be a much faster way, I believe.
>>
>> Thanks for any help, comment and/or suggestion.
>>
>> Vicente Maciel Jr
>>
>

-- 
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/19f96e9e-6225-46e8-bba2-a990a7dbbb34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Data recovery appspot

[James Calfee]

Hi, sorry for the delay.  

The data-store upgrade was shortly after:

7/1/2015

I have attached the email I received about the upgrade.  I was able to 
upgrade my app's front-end, but for some reason I was not able to upgrade 
the data store.  The data-store upgrade required an external tool (command 
line) and I had some issue running it.  I'll be happy to enable support on 
my account (silver or so).  I think I need someone to verify me and fetch 
the data manually.  Or better yet just upgrade it into the new front-end 
app so I can get to the blobstore again.

Here is the email about the data upgrade:

Dear App Engine Developer, 

You are receiving this email because you are listed as an owner of a Google 
App Engine application that is configured to use the deprecated service 
Master/Slave Datastore, which will soon be shut down. Don’t worry though, 
this email gives clear instructions for what you need to do. Even if your 
application does not store data in Master/Slave Datastore, it is still 
configured to use Master/Slave Datastore, so please keep reading. 

When we launched App Engine, Master/Slave Datastore was the only database 
service that applications could use to store data. Master/Slave Datastore 
had issues scaling with the size and complexity of applications running on 
App Engine, so we launched its successor, High Replication Datastore (HRD), 
in 2011. Since that launch HRD has proven to scale without issues 
.
 


One of our core goals with Google Cloud Platform is to provide customers 
with the best technologies to build their business, so when we saw that HRD 
was a more robust technology, we decided to make HRD the default database 
service. On April 4 2012 we announced 

 
the deprecation of Master/Slave Datastore -- our signal that three years 
from that date we would formally shut down the service. 

That three years is upon us and, as mentioned above, one or more 
applications that you own (listed below) are running on Master/Slave 
Datastore. If you don’t take any action these applications will be shutdown 
on *July 6, 2015* and will no longer serve traffic (users will see HTTP 404 
responses). 

To ensure that these applications continue to operate, you’ll need to 
follow these few steps for each application:

   - Log into the Google Developers Console 
   .
   - Create a new project, which in turn creates a new HRD application.
   - Use the HRD Migration Utility 
    to 
   migrate any Master/Slave data to the new HRD application.


*An important note*: You need to follow the above steps even if your 
application does not store any data because your application is *configured* 
to use the Master/Slave Datastore. For example, even if it’s a static HTML 
website. When we shut down the Master/Slave Datastore these applications 
will be also shut down if they are not migrated. 

*For applications on the Java 6 runtime*: Java 6 apps must be upgraded to 
Java 7 prior to the migration to HRD. 
To determine whether your app is a Java 6 app:

   - Visit the App Engine Admin console , 
   and select your application.
   - In the left navigation pane, click *Versions* to display the versions 
   page.
   - At the top of this form, click *Try the new Versions page*.
   - The Java runtime used by your app will be listed under *RUNTIME*.


To upgrade:

   - Update your development environment to use the latest App Engine Java 
   SDK.
   - Redeploy your app to production App Engine.
   - Test it for correct behavior. There are a small number of potential 
   compatibility issues 
    
   between Java 6 and Java 7.

 

-- 
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/220a52a6-fb99-49e7-a628-6a81b4668295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Not able to deploy on app engine standard environment

[Ignazio Aleo]

Hi George,

thanks for the reply (and sorry for my late one). Indeed the issue is now 
gone and I am fully able to deploy without modifications on my side.

Best,
Ignazio

On Thursday, 8 June 2017 18:37:25 UTC+2, George (Cloud Platform Support) 
wrote:
>
> Hello Ignazio, 
>
> This result might be related to a temporary issue with deployments, that 
> should be fixed quite soon. 
>
> On the other hand, if you say you feel guilty about it, you might have 
> somehow contributed to the reported situation. We need more information to 
> start a proper investigation. To enable a closer examination of your 
> installation it may be advisable to run the following commands: 
>
>  
>
> gcloud components update
>
> gcloud info
>
> gcloud app deploy --verbosity debug
>
>  
>
> What is the output from these commands?
>

-- 
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/8c179b5a-7714-429d-a260-48b5c0bb1ad1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Laravel deployment using Google App Engine: No such file or directory

[Adeel Ahmad]

Hi George,

I have gone through the tutorial again and these are the steps which differ 
from it:


   1. I haven't added the following script in my composer.json file as it 
   causes some errors during deployment:
   
   *"post-deploy-cmd": [
   "php artisan cache:clear"
   ]*
   
   2. In the tutorial, cloud_sql_proxy is installed globally, but I run 
   this from my home directory (*~*). Also, the port used
   in the tutorial is *3306, *but I'm using *3307**,* instead. This is the 
   command that I execute:
   *./cloud_sql_proxy -instances=zoho-portal=tcp:3307 
   -dir="/var/run/mysqld/"*
   I also provide it a path to my socket file, which is not done in the 
   tutorial.
   3. The database in the tutorial is named *laravel*, but I named it 
   *zoho_portal*. I don't think this causes any problems, though.
   
Please let me know if any of the above mentioned differences let you debug 
the problem. Also, the source code is hosted on my 
GitHub repository . This might 
help you run this from your end.


Thank you,

Adeel



On Saturday, June 17, 2017 at 1:50:19 AM UTC+5, George (Cloud Platform 
Support) wrote:
>
> Hi Adeel!
>
> The tutorial you mentioned surely works well. What steps differ in your 
> case, from the tutorial? Any small detail may count, so if you provide an 
> exhaustive list of differences, you enable us to properly reproduce the 
> issue on our side. 
>

-- 
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/7a88640e-ac21-4bac-a18e-4b9e63a37727%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to access Google Cloud SQL Proxy from App Engine from DotNet App

[Adriaan Stander]

Using the recommended way of connecting a .Net application running in App 
Engine Flexible .Net to SQL AppEngine Flex 
 (all 
networks allowed to connect to MySql Instance with SSL) we saw many 
unauthenticated logon attempts that we assume have caused some of our 
connection issues recently.


Is there no better(More Secure) way to connect?


Can't we use Google Cloud SQL Proxy to rather connect and limit authorized 
networks using standard capability?


Its seems like only dotnetcore apps that are required to directly connect 
to it 

 (MySQL 
GCLOUD)

On Tuesday, 28 March 2017 15:38:11 UTC+2, Jordan (Cloud Platform Support) 
wrote:
>
> You are correct, the easiest way to connect to your Cloud SQL instance 
> from App Engine, as previously recommended, is to directly connect to it 
> 
>  
> using the Cloud SQL instance's IP address. It is recommended though to 
> include the SSL cert when making the connection if you plan on running your 
> app from your local development environment. 
>

-- 
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/4f210a38-b48b-44bf-942d-174f10050ba1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Search limit

[Emlyn]

There's a documented rate limitation on the search api (which I am hitting
:-( ), of

   - 15,000 Documents added/deleted per minute

https://cloud.google.com/appengine/quotas#search

Is this per index, or for my entire app?

-- 
Emlyn

https://medium.com/the-infinite-machine - A publication about Google App
Engine
sutllang.com - My language sUTL
https://plus.google.com/u/0/100281903174934656260 - Google+

-- 
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/CAMp1VPCd1cvSDoZ-vZPEzxjSn2P5euuiLnNRDq95Qi01m%2B2zBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.