Les applications doivent souvent servir des fichiers statiques tels que JavaScript, des images et CSS en plus de gérer les demandes dynamiques. Les applications de l'environnement flexible peuvent diffuser des fichiers statiques à partir d'une option Google Cloud telle que Cloud Storage, les diffuser directement ou utiliser un réseau de diffusion de contenu (CDN) tiers.

## Diffuser des fichiers depuis Cloud Storage
Cloud Storage peut héberger des ressources statiques pour des applications Web dynamiques. Les avantages d'utiliser Cloud Storage au lieu de diffuser directement à partir de votre application incluent :
- Cloud Storage fonctionne essentiellement comme un réseau de diffusion de contenu. Cela ne nécessite aucune configuration particulière car, par défaut, tout objet lisible est mis en cache dans le réseau global Cloud Storage

- La charge de votre application sera réduite en déchargeant les ressources statiques de diffusion vers Cloud Storage. En fonction du nombre de ressources statiques dont vous disposez et de la fréquence d'accès, cela peut réduire considérablement le coût d'exécution de votre application.

- Les frais de bande passante pour accéder au contenu peuvent souvent être inférieurs avec Cloud Storage

Vous pouvez importer vos éléments dans Cloud Storage à l'aide de la
outil de ligne de commande gsutil
ou l'API Cloud Storage

La bibliothèque cliente Google Cloud fournit un client idiomatique à Cloud Storage, pour stocker et récupérer des données avec Cloud Storage dans une application App Engine

 Exemple de diffusion à partir d'un bucket Cloud Storage
Cet exemple simple crée un bucket Cloud Storage et importe des éléments statiques à l'aide de l'interface de ligne de commande Google Cloud :
Créez un seau. Il est courant, mais pas obligatoire, de nommer votre bucket d'après l'ID de votre projet. Le nom du bucket doit être unique au monde

gsutil mb gsyour-bucket-name>Définir l'ACL pour accorder un accès en lecture aux éléments du bucket

gsutil defacl set public-read gsyour-bucket-name>Importez des éléments dans le bucket. Le
rsynccommand est généralement le moyen le plus rapide et le plus simple de télécharger et de mettre à jour des ressources. Vous pouvez également utiliser
CP

gsutil -m rsync -r ./static gsyour-bucket-name>/static
Vous pouvez maintenant accéder à vos actifs statiques via
httpsstorage.googleapis.com//static

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

 Serving files from other Google Cloud services
You also have the option of using Cloud CDN or other Google Cloud storage services

## Serving files directly from your app
Serving files from your app is typically straightforward, however, there are a couple drawbacks that you should consider:
- Requests for static files can use resources that otherwise would be used for dynamic requests


- Depending on your configuration, serving files from your app can result in response latency, which can also affect when new instances are created for handling the load

 Example of serving static files with your app
 Go
In Go, you can use the standard
http.FileServer
or
http.ServeFile
to serve files directly from your app

// Package static demonstrates a static file handler for App Engine flexible environment. package main import ( "fmt" "net/http" "google.golang.org/appengine" ) func main() { // Serve static files from "static" directory. http.Handlestatic http.FileServer(http.Dir http.HandleFunc homepageHandler) appengine.Main() } const homepage = doctype html>   Static Files /main.css">   
This is a static file serving examplep> 
   Static Files /styles.css">   
This is a static file serving examplep> 
 default 
doctype html html(lang="en") head title Static Files meta(charset='utf-8') link(rel="stylesheet", hrefstatic/main.css") body p This is a static file serving example

The stylesheet itself is located at
./public/css, which is served from
/static/main.css

body { font-family: Verdana, Helvetica, sans-serif; background-color: #CCCCFF; }
Other Node.js frameworks, such as Hapi, Koa, and Sails typically support serving static files directly from the application. Refer to their documentation for details on how to configure and use static content

 PHP
The PHP runtime runs nginx
to serve your app, which is configured to serve static files in
your project directory. You must declare the document root by specifying
document_root in your
app.yaml file:
runtime: php env: flex runtime_config: document_root: web
 Python
Most web frameworks include support for serving static files. In this sample,
the app uses Flask's built-in ability
to serve files in
./static directory from the
/static URL

The app includes a view that renders the template. Flask automatically
serves everything in the
./static directory without additional configuration

import logging from flask import Flask, render_template app = Flaskname @app.route def hello return render_template('index.html') @app.errorhandler(500) def server_error(e): logging.exception('An error occurred during a request returnAn internal error occurred:  See logs for full stacktrace. format(e), 500 if __name__ == main # This is used when running locally. Gunicorn is used to run the # application on Google App Engine. See entrypoint in app.yaml. app.run(host='127.0.0.1', port=8080, debug=True)
The template rendered by the view includes a stylesheet located at
/static/main.css

   Static FilesFlask automatically makes files in the 'static' directory available via '/static'./main.css">   
This is a static file serving examplep> 

doctype html html head title Serving Static Files link rel="stylesheet" hrefapplication.css" script srcapplication.js" body p This is a static file serving example

The stylesheet is located at
./public/application.css which is served
from
/application.css

body { font-family: Verdana, Helvetica, sans-serif; background-color: #CCCCFF; }
 Ruby on Rails
The Ruby on Rails
web framework serves files from the
./public directory by default. Static
JavaScript and CSS files can also be generated by the Rails asset
pipeline

This example app has a layout view that includes all the app's stylesheets:
doctype html html head title Serving Static Files = stylesheet_link_tag "application", media: "all" = javascript_include_tag "application" = csrf_meta_tags body = yield
The stylesheet itself is a
Sass file located
at
./app/assets/stylesheets/main.css.sass

body font-family: Verdana, Helvetica, sans-serif background-color: #CCCCFF
By default, Rails apps do not generate or serve static assets when running in production

The Ruby runtime executes
rake assets:precompile during deployment
to generate static assets and sets the
RAILS_SERVE_STATIC_FILES environment
variable to enable static file serving in production

 .NET
   Hello Static World   
This is a static html documentp>