Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/appengine/docs/legacy/standard/python/console below:

Setting up your Google Cloud project for App Engine

Stay organized with collections Save and categorize content based on your preferences.

A Google Cloud project contains your App Engine application as well as other Google Cloud resources.

You can perform all of your administrative tasks from the Google Cloud CLI and the App Engine Admin API, including the common tasks covered in this topic.

Before you can deploy your apps to the App Engine standard environment, you typically need to create or set up the following:

1. A Google Cloud project
2. An App Engine application
3. A billing account

You can select or create a new Google Cloud project and App Engine application to create and manage a collection of settings, credentials, and your app's metadata. App Engine requires all projects to enable billing, but you will only be charged if a project exceeds its free quota.

Only the Owner role has privileges to create an App Engine application in a Google Cloud project and that application must exist before any other account can perform tasks on that application. For example, the App Engine application must be created before an account with the App Engine Deployer role can deploy an app using a service account.

After installing Google Cloud CLI, an account with the Google Cloud project Owner role can run the following gcloud commands to create a Google Cloud project and App Engine application:

1. Run the following command to create a Google Cloud project:

   gcloud projects create PROJECT_ID

   Replace PROJECT_ID with the Google Cloud project ID.

2. Run the following command to select a region and create an App Engine application:

   gcloud app create

   More information about App Engine locationshelp_outline

3. Enable billing in the Billing page of the Google Cloud console, see Enabling billing for details.

   Tips:
   • If you deploy your apps with the gcloud app deploy command, the gcloud CLI will ensure that your Google Cloud project includes an App Engine application and prompt you to select a region when needed.
   • To check if an App Engine application exists in your Google Cloud project, you can run the gcloud app describe command.

To programmatically create a Google Cloud project and App Engine application, you use both the Cloud Resource Manager API and App Engine Admin API:

1. To create a Google Cloud project, see Creating a New Project.

2. To create an App Engine application, see Creating App Engine Applications.

3. Enable billing in the Billing page of the Google Cloud console, see Enabling billing for details.

To create a Google Cloud project and App Engine application with billing enabled:

1. Go to the App Engine page:

   Go to App Engine

2. Select or create a Google Cloud project.

3. In the Create App page, select a region, service account, and enable billing:

   1. Select a region to specify where you want to your App Engine application located.
      More information about App Engine locationshelp_outline
   2. Select a service account for your app from Identity and API access.
   3. Select or create a billing account to enable billing in your project.

After the App Engine application is created in your project, the Dashboard page opens.

App Engine is regional, which means the infrastructure that runs your apps is located in a specific region, and Google manages it so that it is available redundantly across all of the zones within that region.

Meeting your latency, availability, or durability requirements are primary factors for selecting the region where your apps are run. You can generally select the region nearest to your app's users, but you should consider the locations where App Engine is available as well as the locations of the other Google Cloud products and services that your app uses. Using services across multiple locations can affect your app's latency as well as its pricing.

You cannot change an app's region after you set it.

If you already created an App Engine application, you can view its region by doing one of the following:

• Run the gcloud app describe command.

• Open the App Engine Dashboard in the Google Cloud console. The region appears near the top of the page.

To deploy your apps, you must enable billing. Your account will not be charged if you stay within your free quota. If your application needs resources that exceed the free quota, you will be charged for the additional usage.

If you have a billing account when you create a Google Cloud project, then billing is automatically enabled on that project.

To enable billing on a Google Cloud project:

1. In the Google Cloud console, go to the Billing page:

   Go to Billing

2. Select or create a Google Cloud project.

3. Depending on if a billing account exists or if the selected Google Cloud project is associated with an account, the Billing page displays one of the following:

   • If billing is already enabled for the selected Google Cloud project, then the details about the billing account are listed.

   • If no billing account exists, you are prompted to create a billing account and associate it with the selected Google Cloud project.

   • If a billing account exists, you are prompted to enable billing if the selected Google Cloud project is not already associated with a billing account. You can also click Cancel and then click Create account to create and associate a new billing account.

After you enable billing, there is no limit to the amount that you might be charged. To gain more control over your application's costs, you can create a budget and set alerts.

Use the Billing page to manage your billing accounts:

1. Go to the Billing page in the Google Cloud console:

   Go to Billing

2. Select the account that you want to manage and then navigate to the corresponding page to perform the following management tasks:

   • See an overview of your billing account, make payments, and add billing account administrators from the Overview page.
   • Create budgets and alerts on the Budgets & alerts page.
   • View your transaction history and download invoices from the Transactions page.
   • Export your billing data to a BigQuery Dataset from the Billing export page.
   • Configure your payment account and contacts on the Payment settings page.
   • Set the method of payment on the Payment method page.

For more information about billing, see the Pricing page.

You can create a budget for a Google Cloud project to avoid surprises on your bill and monitor all of your Google Cloud charges from one place. With a budget, you can create alerts that send emails to your billing administrators when charges exceed a certain amount.

To create a budget and set alerts in a Google Cloud project:

1. In the Google Cloud console, go to the Billing page:

   Go to Billing

2. Click the billing account for which you want to create a budget.

3. Click Budgets & alerts and then Create budget to begin creating a budget for your Google Cloud project.

4. Define your budget in the Set budget section and then specify the percentages for which you want to receive email alerts in the following Set budget alerts section.

5. Click Save to set the budget and enable alerts for your Google Cloud project. If you have multiple Google Cloud projects, you must individually set budgets and alerts in each project.

You can specify the project ID in a few different ways:

• By using gcloud init when you install the Google Cloud CLI. To view the default project ID of the gcloud CLI, run gcloud config list.
• By using the gcloud config set project [YOUR_PROJECT_ID] command to set the default project ID of the gcloud CLI.
• By using the --project flag when you deploy your app, for example: gcloud app deploy --project [YOUR_PROJECT_ID]

If you use the Java runtime, you can specify the project ID during deployment using the Google Cloud plugin for IntelliJ or the Google Cloud plugin for Eclipse.

Disable an App Engine application to stop your app from running instances and serving requests. No data loss will occur when you disable your app, nor will any configuration settings change. Simply re-enable your App Engine application to startup instances and continue serving the traffic to your app.

Your app's resources in both the standard and flexible environment are disabled and therefore, won't incur charges. However, billing charges can still occur for the other services in your Google Cloud project, for example you can still incur storage charges for your stored data.

If your app is actively processing a request, it will continue to complete that task and can take up to an hour before your app is completely disabled.

To disable an App Engine application:

1. Go to the Application settings page:

   Go to Application settings

2. Click Disable application and then follow the prompts.

When you want your app to continue serving requests, enable the App Engine application by returning to the same Application settings page and then clicking Enable application.

Disabling your application stops all serving requests, but your data and state are retained. You will still be billed for applicable charges already incurred or charges for other services running in your project, such as Cloud SQL. To release all the resources used within the project, shut down your project.

You can disable billing and release all the Google Cloud resources that are being used in your Google Cloud project by shutting down that project.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["A Google Cloud project can contain one App Engine application, which is regional and cannot be relocated after creation, requiring billing to be enabled for deployments."],["Creating an App Engine application in a Google Cloud project requires Owner role privileges, and the application must exist before other roles can perform tasks on it."],["You can use the `gcloud` CLI, the Cloud Resource Manager API, and App Engine Admin API, or the Google Cloud console to create and manage your projects and applications."],["Billing is required for App Engine applications, but charges only occur when exceeding the free quota, and you can create budgets and alerts to manage costs."],["You can disable an App Engine application to stop serving requests without losing data, and completely shut down a project to release all Google Cloud resources."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4