Configuration Overview

StrictOps uses a single configuration file, strictops.yml, placed in the root of your repository to define how your application should be deployed.

Configuration File

Create a file named strictops.yml in your repository root:

version: 1
services:
  web:
    type: web                 # default, can be omitted
    profile: small            # default, can be omitted
    replicas: 1               # default, can be omitted
    healthcheck_path: /health # default, can be omitted
deploy:
  capacity: serverless        # default, can be omitted
  profile: small              # default, can be omitted
  replicas: 1                 # default, can be omitted
  healthcheck_path: /health   # default, can be omitted
  environments:               # default, can be omitted
    - dev
    - prod
  production:                 # default, can be omitted
    - prod
database:
  enabled: true               # default, can be omitted
monitoring:
  enabled: true               # default, can be omitted

The minimal version of this config is just:

version: 1
services:
  web:
    type: web

All other fields above use their default values and can be omitted.

Next Steps

strictops.yml Reference - Complete reference for all configuration options
Examples - Example configurations for common scenarios

Configuration Overview

Configuration Overview

Configuration File

Next Steps

On this page