Serve static sites
Back to home
On this page
Static site generators are a popular way to create fast sites. Because there’s no need to wait for responses from servers, the sites may load faster.
To learn how to serve your static site using Upsun, you can start with the required minimal app configuration and build on it, or jump straight to an example of a complete configuration.
Minimal app configuration 
To successfully serve a static site using Upsun, you need to set up a minimal app configuration similar to the following:
applications:
app:
# The type of the application to build.
type: "nodejs:22"
source:
root: "/"
# The web key configures the web server running in front of your app.
web:
locations:
/:
# Static site generators usually output built static files to a specific directory.
# Define this directory (must be an actual directory inside the root directory of your app)
# as the root for your static site.
root: "public"
# Files to consider when serving a request for a directory.
index:
- index.htmlSee more information on the required minimal settings:
Add more features
Allow static files but not dynamic files on PHP containers
If you have a PHP container, you might want to enable client-side scripts but disable server-side scripts.
To enable static files that don’t match any rule while disabling server-side scripts on a PHP container, use the following configuration:
applications:
app:
# The type of the application to build.
type: "nodejs:22"
source:
root: "/"
web:
locations:
'/':
...
scripts: false
allow: trueSee more information on locations properties.
Create cache rules
You can create sensible cache rules to improve performance. For example, if you publish new content regularly without updating images or site files much, you might want to cache text files for a day but all image files for longer.
To do so, use a configuration similar to the following:
applications:
app:
# The type of the application to build.
type: "nodejs:22"
source:
root: "/"
web:
locations:
'/':
...
expires: 24h
rules:
\.(css|js|gif|jpe?g|png|svg)$:
expires: 4wYou can also set a Cache-Control header in your rules.
web:
locations:
'/':
...
expires: 24h
rules:
\.(css|js|gif|jpe?g|png|svg)$:
headers:
Cache-Control: "public, max-age=2419200, immutable"
If `expires` and a `Cache-Control` header are set, the rule ignores the `expires` and sets only the `Cache-Control` header. For this reason, make sure
to add a `max-age` value, in seconds, for the `Cache-Control` header.
### Conserve the server
Because your site is completely static, it doesn't need the server to be running.
To set a background process that blocks the server and conserves resources,
use the following configuration:
```yaml {configFile="app"}
applications:
app:
# The type of the application to build.
type: "nodejs:22"
source:
root: "/"
web:
commands:
start: sleep infinityYou can also use this place to start small programs, such as a script to handle 404 errors.
Complete example configuration
applications:
app:
# The type of the application to build.
type: "python:3.9"
source:
root: "/"
web:
locations:
'/':
# The public directory of the application relative to its root
root: 'public'
# The files to look for when serving a directory
index:
- 'index.html'
# Disable server-side scripts
scripts: false
allow: true
# Set caching policy
expires: 24h
rules:
\.(css|js|gif|jpe?g|png|svg)$:
expires: 4w
commands:
# Run a no-op process that uses no CPU resources since this is a static site
start: sleep infinity