Note: Services were previously called "modules", and services are still declared in
app.yaml files as modules, for example:
Directory structureEach version of a Go service is defined in an
app.yamlfile. The YAML file usually takes the same name as the service it defines, but this is not required. If you are deploying several versions of a service, you can create multiple yaml files in the same directory, one for each version.
app.yaml configuration file defines the scaling type and the CPU, disk,
and memory resources for a specific version of a service.
queue.yaml) are included in the top level app directory. The example below shows three services. In service1 the source files are contained in a subdirectory, in service2 they are at the same level as the yaml file; service3 has yaml files for two versions:
For small, simple projects, all the app's files can live in one directory:
The default service
Every application has a single default service. The default service is
app.yaml with the setting
Optional configuration files
These configuration files control optional features that apply to all the services in an app:
To deploy and apply these configuration settings to your App Engine environment, use:
gcloud app deploy dispatch.yaml gcloud app deploy index.yaml gcloud app deploy cron.yaml