[Release] Automated deployment on Google Cloud App Engine (Autoscale, zero-downtime deploy, autohealing)

Github repo: https://github.com/EducationLink/meteor-google-cloud

We’re migrating our whole infrastructure from AWS to Google Cloud.
Because of that, we wanted a simple way to deploy our Meteor apps on App Engine Flexible.

We created this package to be as simple to deploy as Meteor Galaxy.

  • It uses Google App Engine Flexible with Docker.
  • Session affinity
  • Websockets
  • Health checks

The package takes care of the Docker image, building, bundling and deploying. Can be run from the CLI and of course in your CI pipeline.

Should be as easy as:

meteor-google-cloud --settings config.json --app app.yml --docker Dockerfile 

Feel free to open any issues.


Good job. Does App Engine have auto-scaling?

Yes, it does, it has autoscaling, auto-healing, etc.

Absolutely gorgeous! Nice alternative to mup-aws-beanstalk for sure.


This is super cool. I have a few questions.

  • What are the typical monthly costs you have using this?
  • Does this support pre-rendering for SEO or does that need to be done manually?

Nice work!

Great to see deployment tools like this popping up. Much appreciated!

1 Like

Hello @drew.

I would say that for a standard configuration would be ~$30 per month:


We basically have a wrapper to make it easier to deploy to AppEngine, we didn’t add any extra capability, but whatever you develop or add to your Meteor App will work.

As a heads up to anyone reading this thread, I ran “meteor-google-cloud --init”

And got the error:

error: cp: no such file or directory: C:/Users/Moonshots/AppData/Roaming/npm/node_modules/meteor-google-cloud/dist/libapp.yml

The command added the folders -p and deploy but failed there after.

I may have installed wrong but I double checked several times, then went and looked at the git hub files. Never fear the 3 files you are looking for ( Dockerfile, app.yml and settings.json ) are in the Examples folder. This may just be a user error on my part with your directions. But in case this happens to another person. Just grab the files from the examples folder and fill in the blanks.

Thank you from the bottom of my heart for your repo files! I too am migrating to Google Cloud from AWS.

Aaron Bombay

1 Like

That’s an interesting error, especially running the --init, which is the simplest script possible.
It basically copies cp the files from the examples folder to your project/repo.
I have to admit that our test in Windows machines is limited, but I’ll take a look.

Let me know if you face any problems while deploying the app.

PS: Worth noting that AppEngine may have multiple services (or “apps”), but the first service must be called default. This is not explained in our documentation yet. But the error message from Google is self-explanatory.

This works like a charm.

My only question now is the best practice for connecting to MongoDB Atlas. They (Atlas) seem to want you to whitelist IPs-- is there a common range we can white list or do we need a more complex setup?

@raphaelarias are you guys using atlas by any chance?

1 Like

Hi @a.com.

We do use Atlas, and I love it. Here are some things to consider using Atlas with AppEngine plus some words regarding the IP Whitelist.

  • Atas support GCP so you can keep both in the same zone to lower latency.
  • AppEngine supports VPC (something we used to use with Galaxy and Atlas) but it’s slightly different
  • The GCP Atlas instances are slightly different than their AWS counterparts (sometimes slightly lower ram, but higher IOPS, etc)

So usually we would use a VPC to connect Galaxy (AWS) to Atlas (AWS), but with AppEngine the VPC once setup will not allow you to connect from outside the VPC, like AWS, which can be annoying.

GAE doesn’t have a list of IPs you can whitelist, which is a shame, but you can follow this guide https://stackoverflow.com/questions/11149470/google-app-engine-list-of-ip-addresses to retrieve it. The downside is that Google can change this list without notifying you beforehand.