Skip to main content
Skip to main content

Frequently Asked Questions

Both serve static files with Nginx. The Static service generates the Nginx configuration from a declarative run.routing section (redirects, headers, CORS) and has Prerender.io built in. The Nginx service gives you the default configuration or your own file via run.siteConfigPath, which is the way to go for proxy_pass, caching or extra ports. See the comparison.

run.routing is only read by the Static service. The Nginx service ignores it without an error. Either switch run.base to alpine/static, or express the redirects and headers in a custom configuration set via siteConfigPath.

Prerender.io support is built into the Static service, not into the Nginx service. On the Nginx service you can add the prerender rules to your own configuration set via siteConfigPath, or switch to the Static service.