[google-appengine] App Engine Flex Environment custom domain forwarded to appspot-preview.com

[seongjoo]

My app setup a custom domain on App Engine Flex Environment. The domain is 
forwarded to appspot-preview.com. Clearly, I don't want this to happen.

I have another with same runtime (nodejs) setup a custom domain but it 
didn't have the problem.


-- 
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/83cddbb4-0831-47fd-a369-e50e91c5d7a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Migrating from Endpoints v1 to v2 for AppEngine

[Paul Mazzuca]

In trying to migrate to Endpoints V2 for GAE, I have been unable to get the 
example located at  java-docs-samples/appengine/endpoints-frameworks-v2/backend 
(git clone https://github.com/GoogleCloudPlatform/java-docs-samples) to 
work. Does anyone know where the documentation for localhost testing is? 
Has anyone gotten this example to work locally?  The README does include 
instructions as to how to deploy the project, but nothing on how to test 
locally. 

The process that I have used thus far is:

1.  mvn exec:java -DGetSwaggerDoc
2. mvn appengine:run

Then to test:

 curl \

 -H "Content-Type: application/json" \

 -X POST \

 -d '{"message":"echo"}' \

 http://localhost:8080/_ah/api/echo/v1/echo


The response is a 404.



-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8d633137-4ef5-4b51-8da9-95bb1a18ba02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Uploading large image files and video to Google Cloud Storage

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

The simplest upload option is the POST object call to the XML API 
, which accepts 
form data and allows you to upload a file without any JavaScript using just 
a  tag with the 'action=' attribute set to the Cloud Storage API 
Endpoint, eg.


...

You can of course use an XHR in JavaScript to post the form as well. 
Authentication for this type of upload is done using a policy document, 
which is described in the Usage and Examples 
 
section of the documentation along with Python code examples and an example 
HTML form.

A cleaner approach is to use the Google API JavaScript Client Library 
 
to upload the file using the JSON API 
. There's a JavaScript 
example on the googlearchive GitHub page  
called storage-getting-started-javascript 

 
which I still use as a reference, and is still updated. This will show you 
how to do a multipart upload 
, 
which is sufficient for most files under 5MB. Authentication for this is 
done using OAuth and is handled by the GAPI client.

If you need resumable uploads, it's not too much work to adapt the concepts 
in Performing a Resumable Upload 
, 
which give raw HTTP examples, to the above code example. If you need to do 
some kind of authentication outside of Google OAuth, you can look into Signed 
URLs . 
The documentation also provides Python code samples for generating them 
.
 
Uploading to a signed URL works mostly the same way as for regular GCS 
URLs, with some differences that are covered in the docs.

On Monday, February 20, 2017 at 10:47:26 AM UTC-5, Richard Cheesmar wrote:
>
> I am using the standard python app engine environment and currently 
> looking at how one goes about uploading multiple large media files to 
> Google Cloud Storage (Public Readable) using App Engine or the Client 
> directly (preferred).
>
> I currently send a bunch of smaller images (max 20 - between 30 and 100k 
> on average), at the same time directly via a POST to the server. These 
> images are provided by the client and put in my projects default bucket. I 
> handle the requests images using a separate thread and write them one at a 
> time to the cloud and then associate them with an ndb object. This is all 
> fine and dandy when the images are small and do not cause the request to 
> run out of memory or invoke a DeadlineExceededError. 
>
> But what is the best approach for large image files of 20mb+ a piece or 
> video files of up to 1GB in size? Are there efficient ways to do this from 
> the client directly, would this be possible via the Json api ,a resumable 
> upload, for example? If so, are there any clear examples of how to do this 
> purely in javascript on the client? I have looked at the docs but it's not 
> intuitively obvious at least to me.
>
> I have been looking at the possibilities for a day or two but nothing hits 
> you with a clear linear description or approach. I notice in the Google 
> Docs there is a way using PHP to upload via a POST direct from the client...
> https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is 
> this just relevant to using PHP on app engine or is there an equivalent to 
> createUploadUrl 
> for python or javascript?
>
>
> Anyway, I'll keep exploring but any pointers would be greatly appreciated.
>
>
> Cheers
>
>

-- 
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/5e237918-875f-46b6-b18f-133968af5bc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoint API not working properly via API Explorer after deployment to App Engine Standard

[George Sxi]

Hi Nick ,

Sorry for the delayed reply...been diving in the depths of app engine for a 
while...heh..

Well in my case I had to include the following lines in my 
appengine-web.xml in the android studio :

 
 1
 


my understanding is (and please correct me if I am wrong) that in order to 
use Firebase with App Engine standard environment, manual instance scaling 
must be used because Firebase needs long lived background threads to listen 
and such threads are allowed only on manually scaled instances..
After including this I finally got results to my tests directly from 
Firebase Database.
Let me know if my understanding is correct..

Thanks,
George



On Monday, February 13, 2017 at 10:33:44 PM UTC+2, Nick (Cloud Platform 
Support) wrote:
>
> Hey George,
>
> That's great to hear. Keep in mind that we also monitor our tags on Stack 
> Overflow, so I'll be there as well if you ask a question, haha. Glad to 
> have been of assistance.
>
> One last question I have, though, is what you meant about manual scaling. 
> Could you share some more information about that? How was manual scaling 
> involved in this issue's appearance / solution?
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Saturday, February 11, 2017 at 4:14:37 AM UTC-5, George Sxi wrote:
>>
>> Many thanks for your insight Nick, in my case, apart from the issue you 
>> described I have also forgotten to include "manual scaling" in the relevant 
>> .xml which was causing the issue.
>>  
>> Let me point out that your reply was the fastest and most accurate from 
>> any of my stack overflow posts :) 
>> Will keep in mind to try there first though. 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/887acf1f-39d3-4994-b876-2acfe5a76163%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] nickname field in GAE Standard logs

[PK]

I have noticed that when a user is authenticated the GAE Standard request logs 
(both v1 and v2) have a field called nickname inside protoPayload. This field 
captures the user name but not the domain name. So for example if the logged in 
user is f...@bar.com  this will show ‘foo’. I do not see 
the domain captured in any other field.

Unless I am missing something where would be the right public tracker these 
days to file an enhancement for this?

Thanks
PK
www.gae123.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/FE1406DA-A40C-4DC3-AE95-85642E1C81A2%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Sharing dedicated memcache across different modules of an app engine app

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

Since Google Groups is meant for general product discussions, your coding 
question would be best posted on Stack Overflow 
. I recommend you also 
supply your actual code for both services, as using Namespaces 

 can 
cause this.  

-- 
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/c6040509-d331-4e44-b8f9-25ec9103dbfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine stuck at two instances at idle?

['Zip Zit' via Google App Engine]

I'm a first time user for Google Cloud.   I'm a software developer 
investigating the use of Google Cloud for a customer.  I'm trying to figure 
out how much different stuff costs before committing to a design.  Frankly 
the free tier got me interested in using Google Cloud.  Customer will be 
starting small, but wants the flexibility to grow in the future.  

I built a simple test app using the instructions for the Bookshelf Tutorial 
App at https://cloud.google.com/nodejs/tutorials .   I did this two or 
three days ago.  I've probably had ten hits/ submissions to the site. 
 Nothing fancy.  

What I'm trying to understand is pricing.  As I look at my billing 
summaries (Google Cloud Platform --> Billing --> Transactions --> Detailed 
Transactions View) , I see the biggest charge by far is  "*App Engine Flex 
Instance Core Hours.*"  That had me wondering.  I doubt if I used the site 
for more than 20 minutes total.  

Next step is to go to Google Cloud Platform --> Dashboard --> App Engine 
--> Go to App Engine Dashboard. When I get there, I see a graph.  Select 
All Versions, Instances and then an appropriate time interval... in my 
case, lets use seven days.  Yup, I see a baseline of 2 instances, with a 
short pop up to four (which corresponds to my testing the site...) .  

But what's up with those two instances at idle? Seems expensive for doing 
nothing.  I would have thought there should be zero instances at idle.  Or 
am I just doing this wrong?  

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 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/7c23a6cf-f2f3-456c-9a70-9d3b88fb3637%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: from .appspot.com to .appspot-preview.com

['Zip Zit' via Google App Engine]

Adam.   that word "preview" makes me very nervous.  It implies that there 
are limited services, or that the object viewed is not production ready, or 
the object viewed in this guise is for temporary use only...

What is the catch?  Why did they choose that word? 





. On Saturday, February 18, 2017 at 11:25:33 AM UTC-8, Adam (Cloud Platform 
Support) wrote:
>
> A change was made causing some App Engine Flexible apps to redirect to 
> appspot-preview.com. If you have any client applications that point to 
> the old domain, you'll need to update them to use the new URL.
>
>
>>

-- 
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/80b0ffbc-9296-42e0-b974-3b404fa1e881%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE - python - standard - out of the box / open source CMS solutions

[George Bittmann]

If you do try WordPress I would highly recommend that you do it on Flexible 
as stated by Jordan. WordPress performance on the Standard environment is 
pretty terrible.

On Friday, February 17, 2017 at 10:56:09 AM UTC-5, Jordan (Cloud Platform 
Support) wrote:
>
> You might want to consider hosting your site on Compute Engine 
> . With Google Compute Engine (GCE), 
> you can quickly deploy a wide range of Content Management System 
>  apps 
> via the Cloud Launcher 
> 
> . 
>
> Alternatively if you want to stay on App Engine, you can follow the CMS 
> guide 
>  for 
> deploying WordPress on the App Engine Flexible 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/9a7f2d59-532e-4f3a-8980-09429bb7d651%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE - python - standard - out of the box / open source CMS solutions

['Zip Zit' via Google App Engine]

I have to believe one of the static blog tools would work for you, 
something like this:  https://gohugo.io/ . Easy solution. Safe, secure, no 
fuss, no mess, no hassle. inexpensive. Less is more.

>
>

-- 
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/534a1743-1083-46da-b4d4-c205f41096a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: deploy is very slow

[Alex Komoroske]

I'm running into this too with the Go flexible environment. Deploys are 
taking 30+ minutes.

On Monday, February 13, 2017 at 12:44:20 PM UTC-8, Nick (Cloud Platform 
Support) wrote:
>
> Hey Luis, 
>
> The best way in fact would be to create a Public Issue Tracker 
> thread, and 
> we'll be able to follow up there. Post the link here once you've created a 
> thread, and I'll be happy to assist, sending you an email which you can 
> reply to, attaching the log. 
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Sunday, February 12, 2017 at 11:57:14 AM UTC-5, Luis F De Pombo wrote:
>>
>> Hi Nick,
>> I am having the same issue as Adam but I am using a nodejs Flex env. I 
>> have the file you point to, what is the best email to get this to you? 
>> Thank you.
>>
>> On Monday, February 6, 2017 at 10:40:48 AM UTC-8, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Just a quick update:
>>>
>>> As well, to avoid the timestamp filtering commands above, you could 
>>> simply run the deployment with the --verbosity debug and --log-http flags 
>>> and then run gcloud info to check for where the "latest log file" is 
>>> stored, and upload that file. The output line telling its location will 
>>> look like:
>>>
>>> Last Log File: 
>>> [/home/anon/.config/gcloud/logs/2017.02.06/18.30.49.455744.log]
>>>
>>>
>>> On Monday, February 6, 2017 at 12:58:05 PM UTC-5, Nick (Cloud Platform 
>>> Support) wrote:

 Hey Adam,

 Could you capture the deployment logs using the flags "--verbosity 
 debug" and "--log-http", piping this output into the "ts" utility to 
 prepend a timestamp to each line, and then email me the logs? I'll be able 
 to analyze what might be going on that way. On linux / Mac that will look 
 like:

 gcloud --quiet --verbosity debug --log-http app deploy app.yaml 
 --version ${VERSION} 2>&1 | ts | tee -a deploy_log.txt 


 (tee is used so that you can still read the output as it hits the 
 console, and note that you'll have to put whatever version you want in the 
 command where ${VERSION} is written)

 On windows, you can use powershell to run the same command line after 
 creating the "ts" filter to prepend timestamps by running the following 
 line:

 filter timestamp {"$(Get-Date -Format s): $_"}


 Cheers,

 Nick 

 On Saturday, February 4, 2017 at 2:30:00 AM UTC-5, Adam Mathias 
 Bittlingmayer wrote:
>
> Yes, it is the Flex Env.
>
> Reviewing the container build logs, it does not seem deterministic. 
>  The total time varies, and the place in the process where multiple 
> minutes 
> pass between two log lines varies.
>
>
> On Friday, 3 February 2017 12:40:25 UTC-8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Adam,
>>
>> Are you deploying a Flexible Environment app? If so, what do the 
>> container builder logs from the Console show as far as activity during 
>> this 
>> time?
>>
>> Also, is this still occurring, or was it only for a certain period of 
>> time? If it's transient, it might just be a momentary service 
>> degradation, 
>> which for a Beta product is to be expected at this stage. When a product 
>> goes into General Availability, we'll often have certain Service Level 
>> targets in terms of latency, uptime, that you can rely on (for example, 
>> read 
>> here  for Compute Engine SLA's)
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, February 2, 2017 at 9:02:29 AM UTC-5, Adam Mathias 
>> Bittlingmayer wrote:
>>>
>>> Deployment with gcloud deploy app is slow (in the low dozens of 
>>> minutes).
>>>
>>> The build is fast, it is the push steps that are slow.
>>>
>>> Both steps like Mounted from google_appengine/python and Updating 
>>> service [test]...\ ie steps that are in the datacentre, not the 
>>> upload itself.
>>>
>>> Thus the size of the code seems to have no effect, it is small 
>>> enough in this case.  It happens with both python 2 and 3.
>>>
>>> Is there a way to increase an allocation to speed this up?  Are 
>>> there other factors?
>>>
>>

-- 
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/6ac91660-5285-42d4-bf18-9688b92bd9bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/op

[google-appengine] Uploading large image files and video to Google Cloud Storage

[Richard Cheesmar]

I am using the standard python app engine environment and currently looking 
at how one goes about uploading multiple large media files to Google Cloud 
Storage (Public Readable) using App Engine or the Client directly 
(preferred).

I currently send a bunch of smaller images (max 20 - between 30 and 100k on 
average), at the same time directly via a POST to the server. These images 
are provided by the client and put in my projects default bucket. I handle 
the requests images using a separate thread and write them one at a time to 
the cloud and then associate them with an ndb object. This is all fine and 
dandy when the images are small and do not cause the request to run out of 
memory or invoke a DeadlineExceededError. 

But what is the best approach for large image files of 20mb+ a piece or 
video files of up to 1GB in size? Are there efficient ways to do this from 
the client directly, would this be possible via the Json api ,a resumable 
upload, for example? If so, are there any clear examples of how to do this 
purely in javascript on the client? I have looked at the docs but it's not 
intuitively obvious at least to me.

I have been looking at the possibilities for a day or two but nothing hits 
you with a clear linear description or approach. I notice in the Google 
Docs there is a way using PHP to upload via a POST direct from the 
client...https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is
 
this just relevant to using PHP on app engine or is there an equivalent to 
createUploadUrl 
for python or javascript?


Anyway, I'll keep exploring but any pointers would be greatly appreciated.


Cheers

-- 
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/85f8b4ca-943b-4c70-9a88-a64ecabb4f55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.