Serving from your application
<html> <head> <meta charset="utf-8" /> <title>Hello Static World</title> </head> <body> <p>This is a static html document.</p> <p><img src="trees.jpg" /></p> </body> </html>
To enable static file serving, add this code to your
Serving files from the application is typically straightforward, however, there are drawbacks to this approach. Requests for static files can use resources that otherwise would be used for dynamic requests. Depending on your configuration, this can cause your application to be slow to respond or to create new instances to handle the load. It's recommended best practice to serve static content separately from your application in production.
Serving from Cloud Storage
Cloud Storage can be used to host static assets for dynamic web applications. The benefits of using Cloud Storage instead of serving directly from your application 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 application'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 application by a significant amount.
- Bandwidth charges for accessing content can often be less with Cloud Storage.
Example of serving static files from a Cloud Storage bucket
This simple example creates a Cloud Storage bucket and uploads static assets using the 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 application, see Using Cloud Storage.
Serving from a third-party content delivery network
Your application may use any third-party content delivery network (CDN) to serve static assets and cache dynamic requests. If you use third-party CDN service that has direct interconnect links with Google Cloud Platform you can reduce the latency and cost of your application. For more information, see CDN Interconnect.