[google-appengine] Re: Pushed my site with deploy but old one remains

Hi Nikos, This seems to be a new question: how to detach mapping of your custom domain to your service. You did not mention this purpose till now. For a new question, it is better to open a new thread, but not in Groups. This forum meant for general discussion on the platform and its services,

[google-appengine] Re: Pushed my site with deploy but old one remains

awesome, I deleted the old project to get the custom domain free, any idea how long I need to wait? Point your domain to qunatumvue Google will add a free, auto-renewing SSL certificate to your application for security. The following domain and subdomains will be mapped: - www.quantumjs.com

[google-appengine] Re: Pushed my site with deploy but old one remains

Hi Nikos, Detailing the actions to be taken: 1) redeploy your app with an empty application: you can read needed details on the "Deploying the Application" documentation page . 2) create an a

[google-appengine] Re: Pushed my site with deploy but old one remains

Is there a step by step guide for this? I'm not sure about the steps you propose. On Thursday, January 3, 2019 at 5:59:04 PM UTC+2, George (Cloud Platform Support) wrote: > > Hello Nikos, > > You seem to want to stop your default service, which is not possible. This > is why your button is gre

[google-appengine] Re: Pushed my site with deploy but old one remains

Hello Nikos, You seem to want to stop your default service, which is not possible. This is why your button is greyed out. To stop this service, you need to redeploy your app with an empty application, and create an app.yaml that uses only static files. Once this is done, you can stop your app

[google-appengine] Re: Pushed my site with deploy but old one remains

This UI is confusing, how do I stop this service? On Saturday, December 22, 2018 at 4:22:21 PM UTC+2, Nikos Katsikanis wrote: > > It worked now https://issuetracker.google.com/issues/121345412 > > On Saturday, December 22, 2018 at 1:01:29 PM UTC, Nikos Katsikanis wrote: >> >> Sorry even if I onl

[google-appengine] Re: Pushed my site with deploy but old one remains

It worked now https://issuetracker.google.com/issues/121345412 On Saturday, December 22, 2018 at 1:01:29 PM UTC, Nikos Katsikanis wrote: > > Sorry even if I only put text, I can't submit anything. What component am > I supposed to put? > > > > On Monday, December 3, 2018 at 6:07:25 PM UTC, Katayo

[google-appengine] Re: Pushed my site with deploy but old one remains

Sorry even if I only put text, I can't submit anything. What component am I supposed to put? On Monday, December 3, 2018 at 6:07:25 PM UTC, Katayoon (Cloud Platform Support) wrote: > > Hi Nikos, > > There is a likelihood that you have missed filling some required fields or > your message exce

[google-appengine] Re: Pushed my site with deploy but old one remains

Hi Nikos, There is a likelihood that you have missed filling some required fields or your message exceeds the maximum of the allowed message size. If so, there should be an error message on top of the page. You may send the output of the commands or the long error messages via attachment. --

[google-appengine] Re: Pushed my site with deploy but old one remains

thanks, I can't seem to submit my issue: buttons greyed out On Wednesday, November 28, 2018 at 8:27:10 PM UTC, George (Cloud Platform Support) wrote: > > Hi Nikos, > > You app's logs show errors similar to: > > methodName: "google.appengine.v1.Versions.CreateVersion" > > "status: { >cod

[google-appengine] Re: Pushed my site with deploy but old one remains

Hi Nikos, You app's logs shows errors similar to: methodName: "google.appengine.v1.Versions.CreateVersion" "status: { code: 3 details: [ 0: { @type: "type.googleapis.com/google.rpc.BadRequest" fieldViolations: [ 0: { description: "Value "dist/\1$

[google-appengine] Re: Pushed my site with deploy but old one remains

Hi Nikos, The error remains: "INFO: Previous default version is an automatically scaled standard environment app, so not stopping it. "Are you using manual scaling or automatic scaling in your app.yaml? If you're using manual scaling, App Engine will try to keep instances alive indefinitely un

[google-appengine] Re: Pushed my site with deploy but old one remains

Thx! The yaml runtime: python27 api_version: 1 threadsafe: true handlers: - url: / static_files: dist/index.html upload: dist/index.html - url: /.* static_files: dist/index.html upload: dist/index.html skip_files: - media - node_modules - public - src - tests -

[google-appengine] Re: Pushed my site with deploy but old one remains

Hi Nikos, You should be able to manage versions and set the default one in the Developers' Console, navigating to App Engine --> Versions, where you can stop the unwanted version and start the preferred one. You may read more on the "Testing and Deploying your Application" documentation page

[google-appengine] Re: Pushed my site with deploy but old one remains

Check if there are multiple versions of your app and if the new version has any traffic routed to it, or if the old version is still set to receive all the traffic. Attila -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe fr