[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThe \u003ccode\u003eapp.yaml\u003c/code\u003e file is used to configure an App Engine app, including its runtime, handlers, scaling, and environment variables, and it acts as a deployment descriptor for a specific service version.\u003c/p\u003e\n"],["\u003cp\u003eIf an \u003ccode\u003eapp.yaml\u003c/code\u003e file is not created, the \u003ccode\u003egcloud app deploy\u003c/code\u003e command can automatically generate one containing the necessary settings for the application to run.\u003c/p\u003e\n"],["\u003cp\u003eFor simple Java apps in the standard environment, the \u003ccode\u003eapp.yaml\u003c/code\u003e file typically only requires the \u003ccode\u003eruntime\u003c/code\u003e element, as App Engine provides default values for other settings.\u003c/p\u003e\n"],["\u003cp\u003eYou can use a custom name for your \u003ccode\u003eapp.yaml\u003c/code\u003e file, but you must then specify this file name in the deployment command when using \u003ccode\u003egcloud app deploy\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIn a Maven project, the standard location for the \u003ccode\u003eapp.yaml\u003c/code\u003e file is within the \u003ccode\u003esrc/main/appengine\u003c/code\u003e directory, and if multiple JAR files or a custom entry point are required, you must define it within the \u003ccode\u003eentrypoint\u003c/code\u003e element of \u003ccode\u003eapp.yaml\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Defining runtime settings\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nAn App Engine app is configured using an `app.yaml`\nfile, that contains the runtime, handlers, scaling, and other general settings\nincluding environment variables.\n\n\nAbout `app.yaml` files\n----------------------\n\n\u003cbr /\u003e\n\nYou can specify the runtime configuration for your Java app, including versions and URLs, in the `app.yaml` file. This file acts as a deployment descriptor of a specific [service](/appengine/docs/standard/an-overview-of-app-engine) version.\n\n\u003cbr /\u003e\n\n\nIf you don't create an `app.yaml` file, the `gcloud app deploy` command can\n[create one when you deploy your\napplication](/appengine/docs/standard/testing-and-deploying-your-app#other_deployment_options).\nThe `app.yaml` file that App Engine creates contains only the settings\nthat are required to run your application.\n\n\nGenerally, your `app.yaml` file requires only the `runtime` element for a simple\nJava app in the standard environment, for\nexample:\n\n\n runtime: java21\n\n\nApp Engine provides default values for all other settings, including\nthe [F1 instance class](/appengine/docs/standard#instance_classes), which\ndetermines the memory and CPU resources that are available to your app, and\n[automatic scaling](/appengine/docs/standard/how-instances-are-managed#scaling_types),\nwhich controls how and when new instances of your app are created.\n\nIf you need to override the default settings, create an `app.yaml` file and\nspecify the settings you need. For more information, see\n[`app.yaml` file reference](/appengine/docs/standard/reference/app-yaml).\n\n\nYou can specify a unique name for your `app.yaml` files, but then you must\nspecify the file name with the [deployment\ncommand](/appengine/docs/standard/testing-and-deploying-your-app)\nas well. For example, if you name your `app.yaml` file `service-name-app.yaml`\nor `app.standard.yaml`, then you must deploy your app using either: \n\n gcloud app deploy service-name-app.yaml\n gcloud app deploy app.standard.yaml\n\nTo learn more about structuring multiple services and `app.yaml` files in your app, see [Structuring web services](/appengine/docs/standard/configuration-files).\n\nFor a Maven project, the standard location for `app.yaml` file is under the\n`src/main/appengine` directory. The App Engine Maven plugin will\ncreate a correct `target/appengine-staging` directory containing your JAR\nartifacts and this `app.yaml` file, ready for deployment.\n\nThe following is a sample Maven project structure: \n\n MyDir/\n pom.xml\n [index.yaml]\n [cron.yaml]\n [dispatch.yaml]\n src/main/\n appengine/\n app.yaml\n java/com.example.mycode/\n MyCode.java\n\nIf you have more than one JAR file in your project directory or want to\nspecify a custom entrypoint, you must specify it in the `entrypoint` element of\nyour `app.yaml` file.\n\nAll configuration elements\n--------------------------\n\nFor a complete list of all the supported elements in this configuration file,\nsee the\n[`app.yaml` reference](/appengine/docs/standard/reference/app-yaml)."]]