Nodejs app on Google Cloud App Engine not starting

oystersauce Published at Dev

oystersauce

Good day,

my very basic Nodejs app is deployed on a Google Cloud App Engine instance is not starting. The app works locally, deployment with app deploy runs without error - and on the app instance the app runs successfully when started manually through Cloud shell (with >npm start). However, as soon as the Cloud Shell is closed my app is dead. What am I missing? How do I start-up the app to run permanently?

The app consists of

bot4.js file,
npm dependencies
app.yaml
package.json

app.yaml:

runtime: nodejs8
handlers:
- url: /
  script: auto

package.json:

{
  "name": "blexplorer",
  "version": "1.0.0",
  "description": "",
  "main": "bot4.js",
  "scripts": {
    "start": "node bot4.js"
  },
  "author": "oystersauce",
  "license": "ISC",
  "dependencies": {
    "discord.js": "^11.4.2",
    "request": "^2.88.0"
  }
}

Again, the app is running fine when started through the Cloud Shell but no longer, as soon as the Cloud Shell is closed. Also, it's a super simple discord-bot - hence there is no front-end whatsoever.

EDIT: this is how I thought I started the app manually - but what I did here is starting the app within the cloud shell and not on the app instance:

here is how I deploy the app:

Dan Cornilescu

From GAE perspective the cloud shell is simply a shell on a "local" development machine which just happens to be hosted in the cloud. The instance running the cloud shell has no special relationship with GAE whatsoever.

What you're doing when running npm start is not actually starting the GAE instance, you're just starting a "local" execution of your service, just like when you'd be doing the same on your local machine.

With your configuration GAE should start your app automatically as soon a request for it is received. On an app with a frontend just clicking on the link you circled in the snapshot would get you on it. Since yours doesn't have a frontend it would probably be just started, but you'd have to rely on the dashboard info and/or your app's logs to confirm it is running.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at2020-12-2

Comments

0 comments

From Dev

Related Related

Article

Nodejs app on Google Cloud App Engine not starting

Nodejs app on Google Cloud App Engine not starting

Starting app engine modules in Google App Engine

NodeJs:Unable to connect Google Cloud SQL from Google App Engine

Connection timed out: Nodejs Google App Engine to Cloud MySql

Google Cloud: Storage and App Engine

Google cloud storage with app engine

Google App Engine project not starting in Eclipse

Google Cloud App Engine Flexible Python 2.7 Env Errors starting new threads

Connecting to Google Cloud SQL in Google App Engine

Google cloud endpoint on Google app engine

NodeJS Forge viewer error on Google App Engine

Global variable in Google App engine Nodejs Puppeteer

Google App Engine 502 (Bad Gateway) with NodeJS

Google App Engine using sockets with NodeJs

Not able to run nodejs project on google app engine

Google Cloud Build and App Engine enviroment variables

google app engine free tier and cloud platform

Google App Engine Cloud Endpoints userId is null

google cloud app engine deploy failed

Connecting Google Cloud Memorystore with App Engine service

Google App Engine Cloud SQL connection issue

Google Cloud Datastore and Flask App Engine

Google App Engine Standard Python Cloud Build

Google Cloud Datastore requires app engine?

Disable default healthcheck on Google Cloud App Engine

Google Cloud App Engine - Edit 1 file

Use php extensions in Google Cloud App Engine

Google Cloud App Engine - Default Storage Buckets

Different App Engine Applications in Google Cloud

Google Cloud App Engine Flexbile quota error