[google-appengine] Re: App engine flex deployment fail

I opened a bug report on issue tracker as advised. Thank you On Monday, April 17, 2017 at 12:37:10 PM UTC-7, Adam (Cloud Platform Support) wrote: > > This looks related to an internal config issue. I'd advise opening a bug > report on the issue tracker >

[google-appengine] Unknown project: Firebase Demo Project

Hello all, I know this may not be the best place to ask, but if you could point me to the correct place I would appreciate it. While reviewing my list of Google Project, I found one named "Firebase Demo Project". I don't know where this came from... I've search around in both Google Cloud and

Re: [google-appengine] App Engine Flexible Runtime PHP (5.6) deployed failure: Failed to execute git clone --no-checkout 'gitAtgitlab.com:xxxx/framework-php.git'

Hi Yao, We're thinking to introduce an option to skip running `composer install` for a short term solution, which I think we can provide in weeks. An ideal solution (potentially with KMS) will definitely take longer. Thanks, On Mon, Apr 17, 2017 at 11:48 AM Yao Li wrote: > Hi

Re: [google-appengine] Shared memcache not working on Nodejs

Awesome, just filled out the form! Looking forward to it! On Mon, Apr 17, 2017 at 3:14 PM, 'Justin Beckwith' via Google App Engine < google-appengine@googlegroups.com> wrote: > Yes, it should work great from custom runtimes. > > On Mon, Apr 17, 2017 at 1:07 PM, Geoffrey Arnold < >

Re: [google-appengine] Deployment fails

Greetings! Would you mind filing a bug with these details over at bit.ly/appengine-bug? On Sun, Apr 16, 2017 at 3:27 AM, Roy Lee wrote: > Hello, > > I'm trying to deploy to App Engine Flex env (NodeJS), but I'm constantly > getting the following error. > > *ERROR:

Re: [google-appengine] Shared memcache not working on Nodejs

Yes, it should work great from custom runtimes. On Mon, Apr 17, 2017 at 1:07 PM, Geoffrey Arnold wrote: > Hey Justin, thanks for the pointer! Very exciting. > > Is the memcache Alpha available for custom runtimes in the flexible > environment? > > On Mon, Apr 17, 2017

[google-appengine] Re: API/CLI for uploading SSL Certs for AppEngine

Thanks! On Monday, April 17, 2017 at 10:20:39 AM UTC-7, Lorne Kligerman wrote: > > Hi Rahul, > > There is no API/CLI at the moment, but its in the works and we're not far > off! > > Follow this issue for updates: > https://issuetracker.google.com/issues/35894480 > > Thanks! > > Lorne. > Product

Re: [google-appengine] Shared memcache not working on Nodejs

Hey Justin, thanks for the pointer! Very exciting. Is the memcache Alpha available for custom runtimes in the flexible environment? On Mon, Apr 17, 2017 at 12:30 PM, 'Justin Beckwith' via Google App Engine < google-appengine@googlegroups.com> wrote: > Greetings folks, > Apologies for the

[google-appengine] Re: App engine flex deployment fail

This looks related to an internal config issue. I'd advise opening a bug report on the issue tracker and linking to it in this thread, so we can have the engineering team take a look at it. On Sunday, April 16, 2017 at 10:46:24 PM UTC-4,

Re: [google-appengine] App Engine Flexible Runtime PHP (5.6) deployed failure: Failed to execute git clone --no-checkout 'gitAtgitlab.com:xxxx/framework-php.git'

Hi Takashi, If it takes a lot of time (weeks, months or even longer) to publish the feature supporting private repos, I can definitely make a customized docker image. Thanks, Yao On Monday, April 17, 2017 at 11:33:04 AM UTC-7, Takashi Matsuo (Google) wrote: > > > Hi Yao, > > Sorry for the

Re: [google-appengine] App Engine Flexible Runtime PHP (5.6) deployed failure: Failed to execute git clone --no-checkout 'gitAtgitlab.com:xxxx/framework-php.git'

Hi Yao, Sorry for the trouble. Unfortunately currently the private repos are not supported with the Flexible Environment. We're working on a solution, and we'll keep you updated. Thanks! On Mon, Apr 17, 2017 at 11:25 AM Justin Beckwith wrote: > Apologies for the trouble.

Re: [google-appengine] App Engine Flexible Runtime PHP (5.6) deployed failure: Failed to execute git clone --no-checkout 'gitAtgitlab.com:xxxx/framework-php.git'

Apologies for the trouble. Adding a few folks from the PHP team. On Mon, Apr 17, 2017 at 11:00 AM, Yao Li wrote: > App Engine Flexible Runtime PHP (5.6) deployed failure: > > Failed to execute git clone --no-checkout 'gitAtgitlab.com:/ > framework-php.git' > Cloning into

[google-appengine] App Engine Flexible Runtime PHP (5.6) deployed failure: Failed to execute git clone --no-checkout 'gitAtgitlab.com:xxxx/framework-php.git'

App Engine Flexible Runtime PHP (5.6) deployed failure: Failed to execute git clone --no-checkout 'gitAtgitlab.com:/framework-php.git' Cloning into '/app/vendor//framework'... error: cannot run ssh: No such file or directory fatal: unable to fork The command '/bin/sh -c /composer.sh'

Re: [google-appengine] Shared memcache not working on Nodejs

Greetings folks, Apologies for the confusion here. The memcache support for App Engine flexible is currently in alpha: https://cloud.google.com/appengine/docs/flexible/nodejs/upgrading#memcache_service You can fill out the form to get access, or take a look at the memcache support in redislabs:

[google-appengine] Re: API/CLI for uploading SSL Certs for AppEngine

Hi Rahul, There is no API/CLI at the moment, but its in the works and we're not far off! Follow this issue for updates: https://issuetracker.google.com/issues/35894480 Thanks! Lorne. Product Manager - App Engine On Monday, April 17, 2017 at 9:42:07 AM UTC-7, Rahul Somasunderam wrote: > >

[google-appengine] API/CLI for uploading SSL Certs for AppEngine

Currently, to upload certificates for an AppEngine application, you need to go to a URL like this https://console.cloud.google.com/appengine/settings/certificates?project==default Then you need to use the UI to upload the certificate + privatekey pair. With LetsEncrypt requiring you to renew

[google-appengine] Shared memcache not working on Nodejs

Hi, I am trying out Shared memcache for my project (low volume right now). I am not able to connect to it with the following error: Error when trying to fetch from memcache Error: socket timed out waiting on response. at timeoutHandler (/app/node_modules/memjs/lib/memjs/server.js:206:18) at