prokodo init
Scaffold an optional .prokodo/config.json in the current project directory. Running prokodo verify works without this file — use init only when you want to pin a specific projectType or customise the include list.
prokodo init [options]
Options
| Flag | Type | Default | Description |
|---|---|---|---|
--type <type> | string | — | Pin project type (currently only n8n-node; n8n-workflow coming soon) |
--force | boolean | false | Overwrite existing config |
Behaviour
- Checks whether
.prokodo/config.jsonalready exists in the current directory- If it does and
--forceis not set → prints a warning and exits0without overwriting - If it does and
--forceis set → overwrites
- If it does and
- Validates
--typeif provided (must ben8n-node;n8n-workflowis reserved for a future release) - Writes
.prokodo/config.json:- Without
--type: writes{}(fully automatic at verify time) - With
--type: writes{ "projectType": "..." }
- Without
Output file
Without --type:
{}
With --type n8n-node:
{
"projectType": "n8n-node"
}
| Field | Type | Description |
|---|---|---|
projectType | "n8n-node" | Overrides auto-detection at verify time (n8n-workflow reserved for future use) |
include | string[] | Directories/files to upload (defaults to type-specific list if omitted) |
timeout | number | Cloud verification timeout in seconds (can be overridden per-run with --timeout) |
Examples
- Text output
- --json
# No flags — fully auto-detected at verify time
prokodo init
ℹ projectType: (auto-detected at verify time)
✓ Config created: .prokodo/config.json
# Pin to n8n-node
prokodo init --type n8n-node
ℹ projectType: n8n-node
✓ Config created: .prokodo/config.json
prokodo init --type n8n-node --json
{
"created": true,
"path": ".prokodo/config.json",
"config": {
"projectType": "n8n-node"
}
}
# Create config with automatic type detection (recommended for most projects)
prokodo init
# Pin project type
prokodo init --type n8n-node
# Overwrite an existing config
prokodo init --type n8n-node --force
With version control
The generated .prokodo/config.json is safe to commit:
git add .prokodo/config.json
git commit -m "chore: add prokodo config"
Only credentials.json (in ~/.config/prokodo) should never be committed. Add .prokodo/credentials.json to .gitignore as a safety net (though the CLI stores credentials outside the project anyway).
Exit codes
| Code | Cause |
|---|---|
0 | Config created (or already exists and --force was not set) |
2 | Invalid --type value |