Repository navigation
Configuration
OctoPublisher implements a cascading configuration resolution strategy. You can specify options via command-line arguments, environment variables, local configuration files, or user-level configuration files.
When resolving parameters (such as TenantId, ClientId, AppId), OctoPublisher checks sources in this exact order:
[1] Command-line arguments (--client-id, --app-id, etc.)
|-- Overrides all lower sources
[2] Environment variables (STORE_CLIENT_ID, STORE_APP_ID, etc.)
|-- Recommended for CI/CD secret injection
[3] Local config file (./.octopublish.json)
|-- Workspace-specific defaults
[4] Global user config file (~/.octo/mstore.json)
|-- Developer workstation defaults
Place this file in your project root alongside your solution:
{
"mstore": {
"appId": "9NZXP5WR803J",
"sellerId": "94042650",
"notesDir": "packaging/whatsnew",
"descDir": "packaging/store"
},
"playstore": {
"packageName": "one.obxodka.app",
"track": "internal"
}
}Security Warning: Never commit sensitive secrets (
clientSecret, Azure AD credentials, service account keys) into version control. Keep secrets in environment variables or CI/CD secret managers.
On developer workstations, you can save default credentials once:
{
"tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"clientId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy",
"clientSecret": "your-client-secret-value",
"sellerId": "94042650"
}This file is automatically created or updated when you execute:
octopublish mstore configure-
Начало работы
-
Store as Code
-
Модули магазинов
-
CI/CD и конфигурация
-
Внутреннее устройство