{"id":3062,"date":"2022-09-21T06:46:33","date_gmt":"2022-09-21T06:46:33","guid":{"rendered":"https:\/\/www.checkmateq.com\/blog\/?p=3062"},"modified":"2023-08-03T06:01:48","modified_gmt":"2023-08-03T06:01:48","slug":"google-app-engine","status":"publish","type":"post","link":"https:\/\/www.checkmateq.com\/blog\/google-app-engine","title":{"rendered":"How to Deploy an Application on Google App Engine?"},"content":{"rendered":"

Google App Engine<\/h3>\n

App Engine is a managed service provided by google cloud platform, it provides you the simplest way to deploy and scale your applications in GCP<\/a> and end-to-end application management, it supports Go, Java<\/a>, .Net<\/a>, Node.js<\/a>, PHP<\/a>, python<\/a>, Ruby, using pre-configured run times, you can also use a custom run-time and write code in any language, App engine also supports running containers, Some of the important features of app engine are Automatic load balancing & Auto scaling, Application health monitoring, Application versioning, Traffic splitting .<\/p>\n

Compute engine vs App engine\u00a0<\/strong><\/p>\n

Compute engine is a IAAS<\/a> (infrastructure as a service), it provides more flexibility compared to app engine, here you will be responsible for installing software’s, Choosing Hardware and maintaining availability and many more.<\/p>\n

where App Engine is a PAAS (Platform as a service) serverless\/ fully managed service provided by gcp, you will have less responsibilities and lower flexibility compared to app engine<\/p>\n

App Engine Environments – Comparison<\/h3>\n

App engine provides two different kinds of environments Standard<\/strong> and Flexible<\/strong>, use Standard<\/strong> when you want to run\u00a0 application\u00a0 in pre-configured\u00a0 language specific sandboxes where you will only take of your application, it\u00a0 provides\u00a0 services\u00a0 only for applications\u00a0 using\u00a0 \u00a0Java, Python, PHP, Node.js,<\/a> Ruby , Go .\u00a0 \u00a0If you want to deploy containers use Flexible<\/strong> environment , it makes use of compute engine virtual machines , you can use any runtime\u00a0 as long as you can build a docker image for it, it also provides access to background processes in virtual machines, below given comparison will give a clear understanding of differentiation between both the environments.<\/p>\n

\"\"<\/p>\n

In this blog you can learn to create and\u00a0 deploy a Python3 application on App Engine Standard Environment, before that Install and configure gcloud cli or you can also use cloud shell , if you are using cloud shell please skip installation and continue with initializing part.<\/p>\n

you can launch cloud shell from web console as shown below .<\/p>\n

\"\"<\/p>\n

Installing gcloud CLI<\/strong><\/h3>\n

following steps will only help you to install CLI on Linux 64-bit (x86_64) platform, run below given commands on your command line to download \u00a0Linux 64-bit archive file and extract it .<\/p>\n

curl -O https:\/\/dl.google.com\/dl\/cloudsdk\/channels\/rapid\/downloads\/google-cloud-cli-403.0.0-linux-x86_64.tar.gz\r\ntar -xf google-cloud-cli-403.0.0-linux-x86_64.tar.gz\r\n<\/pre>\n
Now run below given command to install\u00a0 gcloud CLI , and enter yes and give the path when it prompts for<\/p>\n
.\/google-cloud-sdk\/install.sh<\/pre>\n
Initializing gcloud CLI<\/h3>\n
then to initialize gcloud CLI run gcloud init<\/strong> command on your terminal , Select option Log in with a new account<\/strong> when it prompts\u00a0 “choose an account that you would like to initialize with , same is shown in the below given snapshot”<\/p>\n
\"\"<\/p>\n
then a link will be provided which you should copy and open it in your browser\u00a0 and login to your gcp account in order to get authorization code .<\/p>\n
\"\"<\/p>\n
After opening the link in your browser , select the account that you want to authorize with and click on allow ,\"\"<\/p>\n
then copy the authorization code and give it in your terminal<\/p>\n
\"\"<\/p>\n
 <\/p>\n
\"\"<\/p>\n
 <\/p>\n
Check the initialization by using any gcloud command<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Writing the Web App<\/h3>\n
create a folder with any name(helloworld is the name used in this blog) , and create files named app.yaml, main.py, requirements.txt\u00a0 ,<\/p>\n
To deploy your web app to App Engine, you need an\u00a0 configuration file named\u00a0 app.yaml<\/strong> , it defines your web application’s\u00a0 settings for App Engine , main.py\u00a0\u00a0<\/strong> is where the python code for this specific application is present , requirements.txt<\/strong> is where the dependencies of this application are mentioned .<\/p>\n
copy the content into the files as given below
\nmain.py<\/strong><\/p>\n
import flask\r\n\r\n# If `entrypoint` is not defined in app.yaml, App Engine will look for an app called `app` in `main.py`.\r\napp = flask.Flask(__name__)\r\n\r\n\r\n@app.get(\"\/\")\r\ndef hello():\r\n    \"\"\"Return a friendly HTTP greeting.\"\"\"\r\n    return \"Hello World!\\n\"\r\n\r\n\r\nif __name__ == \"__main__\":\r\n    app.run(host=\"localhost\", port=8080, debug=True)\r\n<\/pre>\n
above given code is written using flask frame work , this just gives\u00a0 Hello World! <\/strong> on the website.<\/p>\n
requirements.txt<\/strong><\/p>\n
Flask==2.0.3<\/pre>\n
app.yaml<\/strong><\/p>\n
runtime: python39<\/pre>\n
Now lets deploy this application on google App Engine, go on to your terminal and set the project that you want to deploy on, use below given command.<\/p>\n
gcloud config set project <project-ID><\/p>\n
\"\"<\/p>\n
you can get project-ID by using command gcloud projects list<\/strong><\/p>\n
\"\"<\/p>\n
Now\u00a0 change to the directory where your application files are stored<\/p>\n
cd helloworld<\/pre>\n
Create app using command gcloud<\/a> app create\u00a0 <\/strong> and\u00a0 select the region that you want to deploy your app on, all the app engine commands starts with\u00a0 gcloud <app> , and it starts with gcloud <compute> for compute engine commands.<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Now run the following command to deploy the application.<\/p>\n
gcloud app deploy<\/pre>\n
\"\"<\/p>\n
Then use command gcloud app browse\u00a0\u00a0<\/strong>, it will give you a link to the application or it will directly open your application on the browser.<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
As we successfully deployed the application , lets see how versioning and traffic splitting works in\u00a0 app engine, you can list versions by using gcloud app versions list<\/strong><\/p>\n
\"\"<\/p>\n
Now deploy the application again but with a version tag this time, In production you may have many changes in each version of the application to be deployed , but\u00a0 here I am deploying same\u00a0 deploying same application with a different version tag.<\/p>\n
gcloud app deploy --version=v2<\/pre>\n
here v2 is the version name iam using.<\/p>\n
\"\"<\/p>\n
Once again check for the available versions , observe the highlighted in the following snapshot, traffic is completely diverted to newly deployed version even though both the versions are in SERVING status as we did not split traffic between any versions.<\/p>\n
\"\"<\/p>\n
On your gcp web console go to versions<\/strong>\u00a0in App Engine\u00a0<\/strong>and click on split traffic,<\/p>\n
\"\"<\/p>\n
Click on Add version and select version and traffic weight that you want to divert and save it.<\/p>\n
\"\"<\/p>\n
On your terminal or web console check for the traffic splitting now,<\/p>\n
\"\"<\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
Google App Engine App Engine is a managed service provided by google cloud platform, it provides you the simplest way to deploy and scale your applications in GCP and end-to-end application management, it supports Go, Java, .Net, Node.js, PHP, python, Ruby, using pre-configured run times, you can also use a custom run-time and write code … Continue reading “How to Deploy an Application on Google App Engine?”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":3124,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[3,79,2,71,70,69,68,59,11,78,63,23,16,24,80,8],"_links":{"self":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/3062"}],"collection":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/comments?post=3062"}],"version-history":[{"count":20,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/3062\/revisions"}],"predecessor-version":[{"id":4172,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/3062\/revisions\/4172"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media\/3124"}],"wp:attachment":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media?parent=3062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/categories?post=3062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/tags?post=3062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}