Save and reuse deployment configurations to standardize your team's workflow.
Availability
Deployment templates are available on the Business plan only.
Creating a Template
| Setting | Description |
|---|---|
| Name | Template identifier (used with %%INLINECODE_0%% flag) |
| Description | Optional description for your team |
| Project Type | node, python, go, php, ruby, rust, dotnet, static |
| Port | Container port to expose |
| TTL | Default time-to-live |
| Exec Command | Custom startup command |
| Credentials | HTTP Basic Auth (user:pass) |
| Region | Deployment region |
| IP Allowlist | Default IP restrictions |
| Custom Domain | Default custom domain pattern |
Using Templates from the CLI
Reference a template by name when creating an environment:
prev create . --template stagingAll template settings are applied automatically. You can override any individual setting with CLI flags:
prev create . --template staging --ttl 14d --region eu
Example Templates
Staging Template
Name: staging
Type: node
Port: 3000
TTL: 7d
Region: us
Client Demo Template
Name: client-demo
Type: static
TTL: 14d
Credentials: demo:clientpass
Region: us
Secure Testing Template
Name: secure-test
Type: node
Port: 3000
TTL: 24h
IP Allowlist: 10.0.0.0/8
Region: eu