Running locally
You run your application locally with the native development tools that you usually use.
Deploying your application
Deploy your app using the gcloud beta app deploy command. This command automatically builds a container image for you by using the Container Builder service before deploying the image to the App Engine flexible environment control plane. The container will include any local modifications you've made to the runtime image.gcloud beta app deploy .\bin\Debug\netcoreapp1.0\publish\app.yaml
By default the deploy command automatically generates a new version ID each
time that you use it and will route any traffic to the new version.
To override this behavior, you can specify the version ID with the version
flag:
gcloud beta app deploy .\bin\Debug\netcoreapp1.0\publish\app.yaml --version myID
You can also specify not to send all traffic to the new version immediately with
the --no-promote flag:
gcloud beta app deploy .\bin\Debug\netcoreapp1.0\publish\app.yaml --no-promote
Manually building a container for deployment
To build your container images outside of Google Cloud Platform, you must
first upload your images to a container image repository before you can deploy
your images to App Engine with the gcloud beta app
deploy command.
For example, if you build your container images locally with Docker, you can
push those images to Google Container
Registry and then
specify the URL of your image in the --image-url flag of the command:
gcloud beta app deploy .\bin\Debug\netcoreapp1.0\publish\app.yaml --image-url gcr.io/[MY_PROJECT_ID]/[MY_CONTAINER_IMAGE]
Docker base images for .NET
If you'd like to build a .NET custom runtime application from scratch, you can use this base image in a Dockerfile:
| Runtime | Docker command |
|---|---|
| .NET | FROM gcr.io/google-appengine/aspnetcore:1.0.3 |
Viewing your application
After you deploy your app to App Engine, you can run the following
command to launch your browser and view the app at
http://[YOUR_PROJECT_ID].appspot.com:
gcloud app browse
