[google-appengine] Feature Request: Serve content from default google storage bucket without cross origin javascript

Since there's now a default storage bucket for all google projects, it makes sense to be able to serve javascript files from google storage without having to set up cross domain policy. Also it shouldn't require code to proxy files from storage via app engine. Thanks! -- You received

[google-appengine] Re: Connecting from app engine instance to compute engine instance directly

The sooner the better! On Sunday, April 23, 2017 at 5:30:26 PM UTC-4, Lorne Kligerman wrote: > > If a direct connection between an App Engine standard app to a GCE VM via > an internal IP address is what you're looking for, work is in progress! > When ready for testing I'll be sure to drop a

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

That's great news! It can't come too soon! On Sunday, April 23, 2017 at 5:27:25 PM UTC-4, Lorne Kligerman wrote: > > Hey folks, > > I'm glad to report that this is something that we're actively working on! > Nothing to report at the moment on timing but when ready for some testing > I'll be sure

[google-appengine] Re: Connecting from app engine instance to compute engine instance directly

If a direct connection between an App Engine standard app to a GCE VM via an internal IP address is what you're looking for, work is in progress! When ready for testing I'll be sure to drop a note to this group. Cheers, Lorne. Product Manager - App Engine On Wednesday, April 19, 2017 at

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

Hey folks, I'm glad to report that this is something that we're actively working on! Nothing to report at the moment on timing but when ready for some testing I'll be sure to send a note here. Stay tuned! Cheers, Lorne. Product Manager - App Engine On Saturday, April 22, 2017 at 7:15:31 AM

[google-appengine] Re: Flexible & Standard Appengine - Java

Thanks for this, Adam, that's a great resource that I wasn't aware of until I read your thread response. Your summary of the article was also helpful. On Sunday, April 23, 2017 at 2:44:20 PM UTC-4, Adam (Cloud Platform Support) wrote: > > You can find a comprehensive list of changes in

[google-appengine] Re: 503 error on deploy

I believe I was able to fix the issue. The connection to my local hard drive was faulty and after I connected it to another port I was able to deploy the project without a problem. If this is just a placebo-lucky try however and the error comes back, I will file the issue on the Issue Tracker

[google-appengine] Re: 503 error on deploy

I'd advise filing this on the Issue Tracker and linking back to it here, so we can investigate further. It looks like you're trying to deploy over the same version, so you may also want to test deployment to a new version, or test on a new

[google-appengine] Re: Flexible & Standard Appengine - Java

You can find a comprehensive list of changes in Migrating Services from the Standard Environment to the Flexible Environment. You'll need to migrate your app to use the public APIs instead of the standard environment APIs. The

[google-appengine] Flexible & Standard Appengine - Java

We are on java standard appengine for 5+ years. Just want to know, what is not available in Flexible env that is available in the Standard? What are the showstoppers to move to a flexible appengine env from a Standard appengine. -- Regards, Rajesh *www.VeersoftSolutions.com