#Configuration

The CLI reads configuration from two sources: user credentials and project-level settings.

#Credentials file

Managed automatically by flowingto login and flowingto logout.

Path: ~/.flowingto/credentials.json

{
	"email": "user@example.com",
	"token": "...",
	"server": "https://flowingto.com",
	"userId": "...",
	"expiresAt": "2026-12-31T23:59:59.000Z"
}

You should not edit this file manually.

#Project config

Optionally create a .flowingtorc.json file in your project root to set defaults for CLI commands.

Example:

{
	"collection": "abc123",
	"workspace": "my-team",
	"platform": "ios"
}

#Supported fields

• collection — Default collection ID for upload and watch
• workspace — Default workspace slug for collection commands
• platform — Default platform when creating collections

#Lookup behavior

The CLI searches for .flowingtorc.json starting from the current working directory and walking upward to the filesystem root.

#Override order

When the same value is provided in multiple places, the most specific source wins:

1. Command-line flags (highest priority)
2. .flowingtorc.json
3. Credentials file defaults (lowest priority)