Serving files from App Engine
Configuring your static file handlers
To configure your app to serve the
./public directory from the
you define a handler in your
The following demonstrates how to serve the static files of a sample
./public directory. The template for this app's
instructs the browser to load the
main.css file, for example:
<link type="text/css" rel="stylesheet" href="/static/css/main.css">
./public directory is defined in the
static_dir element of the project's
handlers: - url: /favicon\.ico static_files: favicon.ico - url: /static static_dir: public - url: /.* secure: always redirect_http_response_code: 301 script: auto
handlers section in the above example includes two handlers for URLs.
When App Engine receives a request for a URL beginning with
it maps the remainder of the path to files in the
./public directory. If an
appropriate file is found in the directory, the contents of that file are
returned to the client. All other URLs match the
/.* pattern, and are handled
by your app.
URL path patterns are tested in the order they appear in
the pattern for your static files should be defined before the
For more information, see the
Serving files from GCP
Serving files from Cloud Storage
Cloud Storage can be used to host static assets for dynamic web apps. The benefits of using Cloud Storage instead of serving directly from your app include:
- Cloud Storage essentially works as a content delivery network. This does not require any special configuration because by default any publicly readable object is cached in the global Cloud Storage network.
- Your app's load will be reduced by offloading serving static assets to Cloud Storage. Depending on how many static assets you have and the frequency of access, this can reduce the cost of running your app by a significant amount.
- Bandwidth charges for accessing content can often be less with Cloud Storage.
Example of serving from a Cloud Storage bucket
This simple example creates a Cloud Storage bucket and uploads static assets using Cloud SDK:
Create a bucket. It's common, but not required, to name your bucket after your project ID. The bucket name must be globally unique.
gsutil mb gs://<your-bucket-name>
Set the ACL to grant read access to items in the bucket.
gsutil defacl set public-read gs://<your-bucket-name>
Upload items to the bucket. The
rsynccommand is typically the fastest and easiest way to upload and update assets. You could also use
gsutil -m rsync -r ./static gs://<your-bucket-name>/static
You can now access your static assets via
For more details on how to use Cloud Storage to serve static assets, including how to serve from a custom domain name, refer to How to Host a Static Website.
For more information on how to use the Cloud Storage API to dynamically upload, download, and manipulate files from within your app, see Using Cloud Storage.
Serving from a third-party content delivery network
You can use any external third-party CDN to serve your static files and cache dynamic requests but your app might experience increased latency and cost.
For improved performance, you should use a third-party CDN that supports CDN Interconnect.