CLI

# hotcfg push

Upload a JSON file as the next version of a bin's environment, checked against its schema.

usage

```
hotcfg push <file.json> --bin <bin_id> [--env <env>]
```

Uploads the file as the next version of one environment of a bin. The file must be one JSON value; `-` reads it from standard input. The API checks it against the bin's [JSON Schema](https://hotcfg.run/docs/guides/schemas), publishes it, and purges the edge cache, so apps get it on their next fetch.

terminal

```
$ hotcfg push flags.json --bin mobile-flags --env staging
✓ Pushed flags.json to mobile-flags (staging)
  version  v2
  hash     7ac562a24ad09d989d7a8cc810d64bd108028f013313b206aafba5c182fb951d
  cache    edge purge queued for staging
```

## Flags

| Flag | Default | Description |
| --- | --- | --- |
| `--bin` | required | The bin: an id, or `org-slug/id`. |
| `--env` | `production` | `production`, `staging` or `development`. |

Warning

`push` writes to `production` unless you pass `--env`. In scripts and CI, always pass it, and use a key [limited](https://hotcfg.run/docs/reference/keys) to the environments the job should touch.

## When the schema refuses it

Nothing is published, the command exits with `1`, and each problem is printed with the line in your file, the schema rule and the reason:

terminal

```
$ hotcfg push flags.json --bin mobile-flags --env staging
error: flags.json does not match the schema of bin mobile-flags (1 error)

  flags.json:3  /limits/max_upload_mb
    rule:    /properties/limits/properties/max_upload_mb/type
    message: expected integer, but got string
```

A file that isn't valid JSON is refused before anything is sent, with its line and column:

terminal

```
$ hotcfg push bad.json --bin mobile-flags --env development
error: bad.json:1:8: invalid JSON: invalid character '}' looking for beginning of object key string
```

## Examples

terminal

```
# Generate the config and push it without a file
./scripts/build-flags | hotcfg push - --bin mobile-flags --env development

# Name the organization explicitly
hotcfg push flags.json --bin acme/mobile-flags --env staging
```

Pushing the same content again still makes a new version. Versions beyond your plan's history limit are deleted, oldest first.

Last updated 5 November 2026
