Platform target

Render

Render static sites use a build command plus a publish directory. Nift keeps public/ and writes the equivalent Blueprint configuration.

nift init --target=render

What Nift creates

services:
  - type: web
    name: nift-site
    runtime: static
    buildCommand: nift build
    staticPublishPath: ./public

Change name to the service name you want. The Blueprint is user-owned after initialization.

Build environment

The generated build command expects Nift on Render's build path. Choose an installation mechanism appropriate to the project before connecting the Blueprint.

Routing and headers

Render static sites support redirect/rewrite rules and custom response headers. Those rules can be represented in the Blueprint or managed through the Render UI depending on your preferred source of truth.

When the site needs a backend

Render's dynamic web services are separate resources rather than code executed inside a static site. Keep Nift as the static frontend and connect it to a Render web service/database when the application requires runtime behaviour.

Official references: Blueprint specification, static sites, and redirects/rewrites.