Re: [google-appengine] Re: Remove account from Google Developer application

Hi Nick, Thank you for your reply I don't have more detail available about the transaction. Here I attached the transaction slip. Also when I try to contact Billing team, I'm unable to contact them, because we have to fill a form with billing account detail, project code etc. which I don't have

[google-appengine] Re: My Best App Engine Advice Would Be: Throttle Well

Hey Kaan, I'll echo what Jesse has said about the new efforts in place to provide closer work between the community of developers and Cloud Platform Support, and I look forward to the good discussions that can be had here, as well as working together on stackoverflow and the public issue tracke

Re: [google-appengine] Re: Google App Engine (Question about using Google app engine and Java)

Jap! On Tue, May 26, 2015 at 8:45 PM, Jeff Schnitzer wrote: > You are at the bottom of a very long learning curve. You can surmount it > but you need to start reading basic documentation for all of these > components. When you understand the concepts, then it will be easy to > answer those quest

[google-appengine] Re: My Best App Engine Advice Would Be: Throttle Well

Greetings Kaan, You have brought up concerns in the past over how we handle this group, so I want to share some improvements with you and thank you for your part in inspiring them. - In the interest of reducing confusion about where to post, we have updated our help center documentation

Re: [google-appengine] Re: Google App Engine (Question about using Google app engine and Java)

You are at the bottom of a very long learning curve. You can surmount it but you need to start reading basic documentation for all of these components. When you understand the concepts, then it will be easy to answer those questions. Asking for direct answers to a test is inappropriate; we're not t

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

I'm asking this because Managed VM's are currently only available in US projects , so I'm trying to see if there is another issue happening here. On Tuesday, May 26, 2015 at 1:23:01 PM UTC-4, Ryan (Cloud Platform Support) wrote: > > That means y

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

That means you never got a MVM up and running thats all. Is everyone seeing this problem have EU projects? I am trying to reproduce without luck so far following the instructions. I will continue to look into it. If you can confirm that your projects are in the EU it will help. On Tuesday, May

Re: [google-appengine] Re: Google App Engine (Question about using Google app engine and Java)

Hi Jeff.. yes it's a kind of "expertise test" but I know how to develop it in Java and oracle db (local database where I can use table triggers, JPA and java).. or any kind of other database like (mysql or derbydb).. The problem is that I don't have knowledge on Google Cloud services (which servi

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

Hi Ryan, I have never deployed anything to Google successfully. I'm a Google Cloud noob. What I and everyone else on this thread is trying to do is to follow Google's "Hello world" Node JS tutorial here: https://cloud.google.com/nodejs/getting-started/hello-world The problem is that if you fo

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

I thought this stuff was supposed to be abstracted so we didn't see the underlying compute instance... as James Hutton mentioned, how can we find out? Thanks, James On Tue, May 26, 2015 at 8:48 PM, Ryan (Cloud Platform Support) < rbruy...@google.com> wrote: > Where is the instance located? > >

Re: [google-appengine] Re: Google App Engine (Question about using Google app engine and Java)

This looks suspiciously like some sort of exam question. Jeff On Tue, May 26, 2015 at 7:02 AM, Ryan (Cloud Platform Support) < rbruy...@google.com> wrote: > Salutations Peter, > > Welcome to the forms. There are many ways to do what you want to do. I > will answer from my personal experience but

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

If you have deployed it before without issue you can go here and see what zone. If you have not then I need you to confirm you are deploying the Node.js and the command line you used to deploy it. On Tuesday, May

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

I think it is the EU Data Center. But I can't remember for sure. How can I find out? On Tuesday, 26 May 2015 16:18:15 UTC+1, Ryan (Cloud Platform Support) wrote: > > Where is the instance located? > > On Tuesday, May 26, 2015 at 10:57:29 AM UTC-4, James Hutton wrote: >> >> Hi Ryan >> >> I too hav

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

Where is the instance located? On Tuesday, May 26, 2015 at 10:57:29 AM UTC-4, James Hutton wrote: > > Hi Ryan > > I too have been getting this error. Here is the output from the > "--verbosity debug" option, per your request. I have replaced my app ID on > the 3rd line with "X" but it is oth

[google-appengine] Re: 400 Error when trying to deploy the Node.js helloworld app to appengine

Hi Ryan I too have been getting this error. Here is the output from the "--verbosity debug" option, per your request. I have replaced my app ID on the 3rd line with "X" but it is otherwise verbatim. DEBUG: Host: appengine.google.com DEBUG: _Authenticate configuring auth; needs_auth=False D

[google-appengine] Re: TimeZones causing intermittent NPE

You're right... Somehow the TimeZone field wasn't getting initialized properly. This is still counter to the Java spec, though: the specified TimeZone, or the GMT zone if the given ID cannot be understood . So getTimeZone(null) should return GMT. On Friday, May 22, 2015 at 3:38:02 PM UTC-5, N

[google-appengine] Re: Google App Engine (Question about using Google app engine and Java)

Salutations Peter, Welcome to the forms. There are many ways to do what you want to do. I will answer from my personal experience but you will need to adapt to your specific use case. 1) The user data I would store in the Datastore. It is designed to do such work. I would index the players log

[google-appengine] Re: disable appspot.com

My understanding is, as you rightly said you need to configure this in the App. Personally I'd look for where the HTTP Request is coming from and then 301 redirect it to the page on your domain. A bit like if the request was coming from http://yourdomain.com instead of http://www.yourdomain.com.

Re: [google-appengine] disable appspot.com

Yes, you need to do it at the App level. Can choose to serve redirects to the custom domain, or even return 400/404 status. On 26 May 2015 at 14:24, kal.domains wrote: > I'm serving my app from a custom domain. I don't want it to be available > at the appspot.com domain. What's the easiest way

[google-appengine] disable appspot.com

I'm serving my app from a custom domain. I don't want it to be available at the appspot.com domain. What's the easiest way to achieve this? I'd like to be able to do it at the console level, but I have feeling I'll have to configure it in the app. The app is written in Java. Thanks. -- You re

[google-appengine] Google App Engine (Question about using Google app engine and Java)

Hi,this is my firs post on this group. I'am looking for some clarification about using google app engine with java. I have this kind of problem to resolve: (It's quite simple for me to do this in java and oracle database with oracle tables and triggers but in this case I must use only google

[google-appengine] My Best App Engine Advice Would Be: Throttle Well

I've been using App Engine for probably something like 5 years, I have one major app that has been running for 5 years, it's very well polished, and the traffic and behaviour of the app is very predictable *knocking on wood* I have another app that I've been working on for 3 years, it didn't take