Let's do a quick overview of these commands.įirstly, gcloud components update ensures you have the latest Cloud SDK version. If you haven't been doing App Engine development with gcloud recently, you should run the first four commands (#1-#4) to get set up before moving to the next steps. gcloud app deploy - deploy your App Engine application.gcloud config set project PROJECT_ID - set GCP project ID.gcloud config list - list GCP project configuration settings.gcloud auth login - login to your credentialed account.gcloud components update - update Google Cloud SDK.If you don't have the gcloud command on your machine yet, install the Google Cloud SDK and ensure gcloud is available as part of your execution path and familiarize yourself with the following gcloud commands: (Re)Familiarize yourself w/ gcloud commands The Module 0 folder should have files that look like this, as illustrated with the POSIX ls command: $ lsģ. If not, check out the differences so you can move onto the next lab. For this tutorial, you'll start with the code in Module 0 folder (START), and when you've completed the tutorial, your code should match the Module 1 folder (FINISH). The GAE migration repo has all the code you need. Ensure the project has an active billing account and App Engine (app) is enabled. For the purposes of this tutorial, we recommend you create a brand new project or reuse an existing one for this tutorial. Setup projectĪs an existing developer, your App Engine dashboard likely already shows what services you've got running. These are the primary steps for this migration:īefore we get going with the main part of the tutorial, let's setup our project, get the code, then (re)familiarize you with the gcloud command and deploy the baseline app so we know we started with working code. This codelab shows information technology decision-makers (ITDMs) and developers what the migration steps are, so you can familiarize yourself with this process regardless of which framework you actually migrate to. If Flask is not a desired framework to move your application to, you may select another as long as it does its own routing. This module gives practioners hands-on experience for migrating a simple webapp2 app to Flask, a framework supported by App Engine and many more services outside of Google Cloud, making apps much more portable. Instead, it relies on App Engine, configuration files, and the developer to perform that routing of web traffic to corresponding "handlers." Furthermore, webapp2's core benefits are inextricably tied to App Engine's bundled services, effectively deprecating it even though it works on Python 3 (also see related issue). While webapp2 (see docs) still exists and can be used outside of App Engine as a WSGI-compliant web framework, it does not do its own routing of user requests to the appropriate code in the application. Years later it was replaced by successor webapp2 when the 2.7 runtime deprecated 2.5 in 2013. The webapp framework was bundled when App Engine first launched on Python 2.5 in 2008. Survey How will you use this codelab? Only read through it Read it and complete the exercises
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |