CLI Reference
Complete reference for the Fiberwisecommand-line interface
Table of Contents
Overview
The Fiberwise CLI provides a comprehensive command-line interface for managing Fiberwise applications, agents, and platform infrastructure. It supports multi-provider LLM configurations, agent activation, and complete application lifecycle management.
fiber
. All commands support the --help
flag for detailed usage information.
🚀 Quick Start
Install Fiberwise
pip install fiberwise
Initialize Platform
fiber setup
Start Platform
fiber start
Platform will be available at http://localhost:8000
📦 Installation
The Fiberwise CLI is installed as part of the main Fiberwise package:
Standard Installation
# Install Fiberwise platform and CLI
pip install fiberwise
# Verify installation
fiber --help
Development Installation
# Install with development features
pip install fiberwise[dev]
# Clone and install from source
git clone https://github.com/fiberwise-ai/fiberwise.git
cd fiberwise
pip install -e .
# Install core platform
pip install fiberwise
# Install Python SDK for agent development
pip install fiberwise-sdk
# Install Node.js SDK for app development (optional)
npm install fiberwise-sdk
After installation, verify the CLI is working:
fiber --help
Global Options
These options are available for all commands:
Option | Description |
---|---|
--help |
Show help message and exit |
--version |
Show version information |
Commands
fiber start
Start the Fiberwiseweb server with production or development mode.
fiber start [OPTIONS]
Options
Option | Type | Default | Description |
---|---|---|---|
--port |
integer | 8000 | Port to run on |
--host |
string | 127.0.0.1 | Host to bind to |
--reload |
flag | False | Enable auto-reload for development |
--no-browser |
flag | False | Disable automatic browser opening |
--verbose |
flag | False | Enable verbose output |
--dev |
flag | False | Development mode with auto-reload and Vite integration |
--worker |
flag | False | Enable background worker for processing activations |
--vite-port |
integer | 5556 | Port for Vite dev server (development mode only) |
--database-url |
string | sqlite:///./fiberwise.db | Database URL |
Examples
# Production mode with built assets
fiber start
# Development mode with Vite dev server
fiber start --dev
# Production mode with background worker
fiber start --worker
# Development mode with worker and Vite
fiber start --dev --worker
# Custom port
fiber start --port 3000
# Custom ports for both servers
fiber start --dev --port 3000 --vite-port 3001
fiber setup
Initialize Fiberwisedatabase, storage configuration, and web components. This is required before using any other Fiberwisefeatures.
fiber setup [OPTIONS]
Options
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Show database setup details |
--database-url |
string | sqlite://~/.fiberwise/fiberwise.db | Custom database URL (PostgreSQL/MySQL supported) |
--force |
flag | False | Force re-setup (WARNING: deletes existing data) |
⚠️ Important
Run fiber setup
once before using any other commands. This sets up the entire platform.
What Initialize Does
- Database Setup
- Creates SQLite database at
~/.fiberwise/fiberwise.db
- Applies all database migrations
- Creates default admin user ([email protected])
- Sets up CLI application configuration
- Creates SQLite database at
- Storage Configuration
- Creates
~/.fiberwise
directory structure - Sets up local storage provider (default)
- Configures app bundles directory
- Creates agent storage directories
- Creates
- Web Components
- Clones fiberwise-core-web repository (if not present)
- Installs Node.js dependencies with npm
- Builds Vite frontend assets
- Sets up both simple and advanced web interfaces
Examples
# Basic setup
fiber setup
# With verbose output to see progress
fiber setup --verbose
# Force re-setup (WARNING: loses data)
fiber setup --force
# Use PostgreSQL database
fiber setup --database-url postgresql://user:pass@localhost/fiberwise
Verification
# Check if setup was successful
fiber start --help
# Look for the database file
ls -la ~/.fiberwise/
🔐 fiber account
Manage Fiberwise account configurations for connecting to different environments.
fiber account add-config
Add a new account configuration for API access.
fiber account add-config [OPTIONS]
Options
Option | Type | Required | Description |
---|---|---|---|
--name |
string | Yes | Configuration name (e.g., 'production', 'staging') |
--api-key |
string | Yes | Your Fiberwise API key (starts with 'fw_') |
--base-url |
string | Yes | API base URL |
--set-default |
flag | No | Set this as the default configuration |
Examples
# Add production configuration
fiber account add-config \
--name "production" \
--api-key "fw_1234567890abcdef1234567890abcdef" \
--base-url "https://api.fiberwise.ai" \
--set-default
# Add local development configuration
fiber account add-config \
--name "local-dev" \
--api-key "fw_dev_key_here" \
--base-url "http://localhost:5555"
fiber account list-configs
List all saved account configurations.
fiber account list-configs
Example Output
Available configurations:
* production (https://api.fiberwise.ai) [DEFAULT]
local-dev (http://localhost:5555)
fiber account login
Log in using a configuration and save authentication tokens.
fiber account login [OPTIONS]
Options
Option | Description |
---|---|
--config |
Use specific configuration (default: uses default config) |
fiber account add-provider
Add a new LLM provider with API key directly to the database.
fiber account add-provider [OPTIONS]
Options
Option | Required | Description |
---|---|---|
--provider |
Yes | Provider name (openai, anthropic, google, etc.) |
--api-key |
Yes | Provider API key |
--name |
No | Custom provider name |
Examples
# Add OpenAI provider
fiber account add-provider \
--provider openai \
--api-key "sk-..." \
--name "My OpenAI"
# Add Anthropic Claude provider
fiber account add-provider \
--provider anthropic \
--api-key "sk-ant-..." \
--name "Claude Production"
fiber activate
Activate a Fiberwiseagent by file path.
fiber activate [OPTIONS] FILE_PATH
Arguments
Argument | Type | Description |
---|---|---|
FILE_PATH |
path | Path to the agent file to activate (required) |
Options
Option | Type | Default | Description |
---|---|---|---|
--to-instance |
string | local | Target instance: 'local' for direct execution, 'default' for configured server, or config name |
--verbose |
flag | False | Enable verbose output |
--version |
string | latest | Version of the agent to activate |
--input-data |
string | Input data as JSON string |
Examples
# Basic activation (runs on local instance)
fiber activate ./my_agent.py
# Run on your default configured server
fiber activate --to-instance default ./my_agent.py
# Run on production server with input data
fiber activate --to-instance production --input-data '{"query": "test"}' ./my_agent.py
# With version and verbose output
fiber activate --verbose --version "2.0.0" --input-data '{"key": "value"}' ./agent.py
# Run on staging with verbose output
fiber activate --to-instance staging --verbose ./my_agent.py
💡 Instance Routing
The --to-instance
parameter allows you to choose where your agent runs:
- local: Runs directly on your machine (fastest, no configuration needed)
- default: Runs on your default configured server
- "config-name": Runs on a specific named server configuration
See CLI Instance Routing for detailed information.
fiber functions
Function and pipeline management commands that work directly with local services.
fiber functions [COMMAND] [OPTIONS]
Subcommands
fiber functions list
List all functions in the system.
fiber functions list [OPTIONS]
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Enable verbose output with creation dates |
--search |
string | Search functions by name or description | |
--type |
string | Filter by function type (utility, transform, support_agent) | |
--limit |
integer | 20 | Maximum number of functions to show |
fiber functions show
Show detailed information about a function.
fiber functions show <function_id> [OPTIONS]
Argument | Type | Description |
---|---|---|
function_id |
string | Function ID or name to show details for (required) |
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Show implementation code and execution history |
fiber functions create
Create a new function from a Python file.
fiber functions create <name> [OPTIONS]
Argument | Type | Description |
---|---|---|
name |
string | Name for the new function (required) |
Option | Type | Default | Description |
---|---|---|---|
--description |
string | Function description | |
--type |
string | utility | Function type (utility, transform, support_agent) |
--file |
path | Python file containing the function implementation | |
--verbose |
flag | False | Enable verbose output during creation |
fiber functions execute
Execute a function with optional input data.
fiber functions execute <function_id> [OPTIONS]
Argument | Type | Description |
---|---|---|
function_id |
string | Function ID or name to execute (required) |
Option | Type | Default | Description |
---|---|---|---|
--input-data |
string | Input data as JSON string | |
--verbose |
flag | False | Enable verbose output with execution details |
fiber functions list-pipelines
List all pipelines in the system.
fiber functions list-pipelines [OPTIONS]
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Enable verbose output with creation dates |
--limit |
integer | 20 | Maximum number of pipelines to show |
fiber functions execute-pipeline
Execute a pipeline with optional input data.
fiber functions execute-pipeline <pipeline_id> [OPTIONS]
Argument | Type | Description |
---|---|---|
pipeline_id |
string | Pipeline ID to execute (required) |
Option | Type | Default | Description |
---|---|---|---|
--input-data |
string | Input data as JSON string | |
--verbose |
flag | False | Enable verbose output with execution details |
fiber functions pipeline-status
Check the status of a pipeline execution.
fiber functions pipeline-status <execution_id> [OPTIONS]
Argument | Type | Description |
---|---|---|
execution_id |
string | Pipeline execution ID to check (required) |
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Show detailed input/output data and node results |
Examples
# List all functions
fiber functions list
# Search for utility functions
fiber functions list --search "process" --type utility --verbose
# Show detailed function information
fiber functions show hello_world --verbose
# Create a new function from a Python file
fiber functions create my_function \
--description "Processes data" \
--type transform \
--file ./my_function.py \
--verbose
# Execute a function with JSON input
fiber functions execute my_function \
--input-data '{"name": "FIberwise", "data": [1,2,3]}' \
--verbose
# List all pipelines
fiber functions list-pipelines --verbose
# Execute a pipeline
fiber functions execute-pipeline my-pipeline-id \
--input-data '{"source": "api"}' \
--verbose
# Check pipeline execution status
fiber functions pipeline-status execution-uuid --verbose
fiber worker
Start a worker to process agent activations.
fiber worker [OPTIONS]
Options
Option | Type | Default | Description |
---|---|---|---|
--worker-type , -w |
choice | local | Type of worker to use (local, celery, redis) |
--worker-id |
string | auto-generated | Worker ID |
--max-jobs , -j |
integer | unlimited | Maximum number of jobs to process before stopping |
--timeout , -t |
integer | unlimited | Timeout in seconds for job processing |
--verbose , -v |
flag | False | Enable verbose output |
--config-file , -c |
path | Path to worker configuration file |
fiber list-agents
List all registered agents.
fiber list-agents [OPTIONS]
Options
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Enable verbose output (shows creation date and version count) |
fiber account
Manage Fiberwiseaccount configurations.
fiber account [COMMAND] [OPTIONS]
Subcommands
fiber account login
Log in using a configuration file.
fiber account login --config /path/to/config.json
fiber account add-config
Add a new configuration directly from command-line options.
fiber account add-config --name "production" --api-key "your-api-key" --base-url "https://api.fiberwise.ai" --set-default
fiber account list-configs
List all saved configurations.
fiber account list-configs
fiber account import-providers
Import model providers information from the specified app ID.
fiber account import-providers --app-id app-123xyz --save-to-file --format detailed
fiber account list-authenticators
List saved model providers.
fiber account list-authenticators --format detailed
fiber account add-provider
Add a new LLM provider with API key directly to the database.
fiber account add-provider --provider openai --api-key YOUR_KEY --model gpt-4 --set-default
fiber account provider
Manage model providers with subcommands:
fiber account provider list
- List providers by typefiber account provider default "Provider Name"
- Set default provider
fiber account oauth
Manage OAuth authenticators and connections:
fiber account oauth configure AUTHENTICATOR_ID
- Configure OAuth authenticatorfiber account oauth list-authenticators
- List configured OAuth authenticatorsfiber account oauth auth AUTHENTICATOR_ID
- Start OAuth authentication flowfiber account oauth list-connections
- List OAuth connectionsfiber account oauth revoke AUTHENTICATOR_ID
- Revoke OAuth connection
🚀 fiber app
Modern application management with clean architecture and proper instance routing. UPDATED
fiber app [COMMAND] [OPTIONS]
Core Commands
fiber app install
Install an application from a local directory with automatic manifest detection and bundle creation.
fiber app install [APP_PATH] [OPTIONS]
Arguments
Argument | Type | Default | Description |
---|---|---|---|
APP_PATH |
path | . (current directory) | Path to the directory containing the app to install |
Options
Option | Type | Description |
---|---|---|
-m, --manifest |
path | Path to the app manifest file (JSON or YAML). Auto-detects if not specified. |
--to-instance |
string | Target specific config instance by name (overrides default) |
-c, --config |
string | Configuration profile to use (legacy option) |
--verbose |
flag | Enable verbose output with detailed progress |
Installation Process
- Manifest Detection: Auto-finds app_manifest.json/yaml if not specified
- Manifest Validation: Supports both old and new manifest formats
- API Communication: Sends manifest to backend with proper authentication
- Bundle Creation: Creates ZIP bundle with smart file exclusion
- Bundle Upload: Uploads app files to the platform
- Local State: Saves installation info for future updates
Examples
# Install from current directory
fiber app install
# Install with verbose output (recommended)
fiber app install . --verbose
# Install from specific directory to production instance
fiber app install /path/to/my-app --to-instance production --verbose
# Install with custom manifest file
fiber app install --manifest custom_manifest.yaml --verbose
# Install to specific configuration profile
fiber app install --config development --verbose
fiber app update
Update an existing application with intelligent change detection and optional force updates.
fiber app update [APP_PATH] [OPTIONS]
Arguments
Argument | Type | Default | Description |
---|---|---|---|
APP_PATH |
path | . (current directory) | Path to the directory containing the app to update |
Options
Option | Type | Description |
---|---|---|
-m, --manifest |
path | Path to the app manifest file (JSON or YAML). Auto-detects if not specified. |
--to-instance |
string | Target specific config instance by name (overrides default) |
-c, --config |
string | Configuration profile to use (legacy option) |
-f, --force |
flag | Force update even if no changes detected |
--verbose |
flag | Enable verbose output with detailed progress |
Smart Update Features
- Change Detection: Compares manifest hash and version to avoid unnecessary updates
- Path Validation: Warns if app directory has moved since last update
- Local State Tracking: Uses .fw-data/fw_app_info.json for update history
- Force Override: --force flag bypasses all change detection
Examples
# Smart update (only if changes detected)
fiber app update
# Force update regardless of changes
fiber app update --force --verbose
# Update specific directory to production
fiber app update /path/to/my-app --to-instance production --verbose
# Update with different manifest file
fiber app update --manifest updated_manifest.yaml --force
Update Workflow Best Practices
# 1. Initial Installation
fiber app install ./my-app --verbose
# 2. Development changes
# Edit files, update manifest version, modify agents...
# 3. Smart update (recommended)
fiber app update ./my-app --verbose
# 4. Verification
fiber activate ./my-app/agents/my_agent.py --input-data '{"test": true}'
# 1. Test in development first
fiber app update ./my-app --to-instance dev --verbose
# 2. Deploy to production with explicit versioning
fiber app update ./my-app --to-instance prod --force --verbose
# 3. Rollback if needed (revert manifest, then update)
git checkout HEAD~1 -- app_manifest.yaml
fiber app update ./my-app --to-instance prod --force
# Update across environments with confirmation
for env in dev staging prod; do
echo "Updating $env environment..."
fiber app update ./my-app --to-instance "$env" --verbose
echo "Press Enter to continue to next environment..."
read
done
fiber app oauth
Manage OAuth authenticators for applications with comprehensive authenticator lifecycle management.
Subcommands
Register a new OAuth authenticator using a JSON configuration file.
fiber app oauth register-authenticator [OPTIONS]
Option | Type | Required | Description |
---|---|---|---|
--authenticator-config |
path | Yes | Path to JSON file containing authenticator configuration |
--config-name |
string | No | Account configuration name to use |
--app-dir |
path | No | Application directory containing .fw-data (default: current) |
{
"name": "My Google OAuth",
"provider_type": "google",
"client_id": "your-google-client-id",
"client_secret": "your-google-client-secret",
"scopes": ["profile", "email"],
"redirect_uri": "https://your-app.com/oauth/callback"
}
# Register Google OAuth authenticator
fiber app oauth register-authenticator \
--authenticator-config ./oauth/google.json \
--config-name production
# Register with app in different directory
fiber app oauth register-authenticator \
--authenticator-config ./oauth/github.json \
--app-dir /path/to/my-app
List all OAuth authenticators configured for the current app.
fiber app oauth list-authenticators [OPTIONS]
Option | Description |
---|---|
--config-name |
Account configuration name to use |
--app-dir |
Application directory containing .fw-data |
Delete an OAuth authenticator by ID.
fiber app oauth delete-authenticator [AUTHENTICATOR_ID] [OPTIONS]
Argument/Option | Description |
---|---|
AUTHENTICATOR_ID |
OAuth authenticator ID to delete (required) |
--config-name |
Account configuration name to use |
--app-dir |
Application directory containing .fw-data |
🏗️ Architecture Benefits
Clean Separation of Concerns
- Business Logic: FiberAppManager handles all app operations
- Presentation Layer: CLI commands format output and handle user interaction
- Configuration Layer: Pure utilities without CLI dependencies
Robust Error Handling
- Structured Results: AppOperationResult with success/failure states
- Detailed Messages: Info messages, warnings, and actionable error feedback
- User-Friendly Output: Proper CLI formatting with emojis and colors
Comprehensive Features
- Instance Routing: --to-instance parameter for multi-environment support
- Auto-Detection: Smart manifest finding and format conversion
- Change Detection: Avoids unnecessary updates with hash comparison
- Local State: Persistent app information in .fw-data directory
📈 Migration from Legacy Commands
Legacy Command | New Command | Notes |
---|---|---|
fiber install |
fiber app install |
Clean hierarchy, same functionality |
fiber install --update |
fiber app update |
Dedicated update command with smart detection |
--config |
--to-instance |
Clearer naming for instance targeting |
🔄 Complete Workflows
Development Workflow
# Set up development configuration
fiber account add-config \
--name "dev" \
--api-key "fw_dev_key" \
--base-url "http://localhost:8000" \
--set-default
# Install app for development
fiber app install . --verbose
# Make changes and update
# (Smart detection will skip if no changes)
fiber app update --verbose
# Force update after significant changes
fiber app update --force --verbose
Multi-Environment Deployment
# Install to staging
fiber app install . --to-instance staging --verbose
# Test and validate...
# Deploy to production
fiber app install . --to-instance production --verbose
# Configure OAuth for production
fiber app oauth register-authenticator \
--authenticator-config ./oauth/prod-google.json \
--config-name production
fiber bundle
Bundle management commands.
fiber bundle [COMMAND] [OPTIONS]
Subcommands
fiber bundle create
Bundle a Fiberwiseapplication based on its manifest.
fiber bundle create --app-dir /path/to/app --env prod --verbose
Options
Option | Type | Default | Description |
---|---|---|---|
--app-dir |
path | . | Path to the application directory containing the manifest |
--env |
choice | dev | Build environment (dev, prod, test) |
--verbose |
flag | False | Enable verbose output during bundling |
fiber install
Install Fiberwise applications with automatic build and deployment. This command handles the complete app installation process including building, bundling, and deployment.
fiber install app [DIRECTORY] [OPTIONS]
Primary Usage: App Installation
fiber install app
Install a Fiberwiseapplication from the current directory or specified path. Includes automatic npm build, bundle creation, and deployment.
# Install app from current directory (most common)
fiber install app .
# Install with verbose output (recommended)
fiber install app . --verbose
# Install from specific directory
fiber install app /path/to/my-app --verbose
# Skip automatic build (if already built)
fiber install app . --no-build --verbose
Options
Option | Type | Default | Description |
---|---|---|---|
--verbose |
flag | False | Show detailed installation progress and debugging |
--no-build |
flag | False | Skip automatic npm build (use if already built) |
Installation Process
When you run fiber install app
, the system automatically:
- Dependency Installation: Runs
npm install
if needed - Build Process: Executes
npm run build
(unless --no-build) - Bundle Creation: Creates zip archive from
dist/
directory - Manifest Processing: Validates and processes app manifest
- Upload & Deployment: Uploads bundle to platform
- Route Registration: Registers app routes with router
- Cleanup: Removes temporary installation files
💡 Best Practices
- Always use
--verbose
for debugging installation issues - Ensure your app has a valid
package.json
with build script - Build output should be in
dist/
directory - Remove old
*.zip
files before reinstalling - Use AppBridge pattern in your
index.js
for SDK access
⚠️ Common Issues
Installation Issues
- Build failures: Check that npm is in PATH and build script exists
- Old bundles: Delete existing
*.zip
files in app directory - Missing dist/: Ensure
npm run build
createsdist/
directory - Path issues: Use
.
for current directory or absolute paths
Update-Specific Issues
- No changes detected: Update manifest version or use
--force
flag - Missing .fw-data/: Directory moved after install - reinstall or use
--force
- Stale app info: Delete
.fw-data/fw_app_info.json
and usefiber app install
- Authentication errors: Check API key has proper "api_" prefix handling
- Version conflicts: Increment version in manifest, avoid downgrading versions
Debug Commands
# Check current app state
cat .fw-data/fw_app_info.json
# Force update with full logging
fiber app update --force --verbose
# Test API connection
curl -H "Authorization: Bearer api_your-key" \
http://localhost:6701/api/v1/health
# Validate manifest syntax
python -c "import yaml; print(yaml.safe_load(open('app_manifest.yaml')))"
Example Workflow
# Navigate to your app directory
cd my-fiberwise-app
# Clean up any old bundles
rm -f *.zip
# Install the app with verbose output
fiber install app . --verbose
# App will be available at:
# http://localhost:8000/apps/your-app-name
fiber seed-user
Create a seed user for FIberwise.
fiber seed-user [OPTIONS]
Options
Option | Type | Default | Description |
---|---|---|---|
--username |
string | admin | Username for the new user |
--email |
string | [email protected] | Email for the new user |
--display-name |
string | auto-generated | Display name for the user |
--admin |
flag | True | Make the user an admin |
--password |
string | fiber2025! | Password for the user |
--force |
flag | False | Overwrite existing user if it exists |
Default Credentials (Development)
- Username:
admin
- Email:
[email protected]
- Password:
fiber2025!
- Role: Admin
fiber seed-system-user
Create a seed system user based on the current system user.
fiber seed-system-user --force
Configuration
Configuration Files
Fiberwise CLI uses configuration files stored in ~/.fiberwise/
:
~/.fiberwise/configs/
- Account configurations~/.fiberwise/providers/
- Provider configurations~/.fiberwise/default_config.txt
- Default configuration marker~/.fiberwise/default_provider.json
- Default provider info
Environment Variables
Variable | Description |
---|---|
FIBERWISE_API_KEY |
API key for authentication |
DATABASE_URL |
Database connection URL |
FIBERWISE_MODE |
Application mode (development/production) |
WORKER_ENABLED |
Enable/disable background worker |
Database Configuration
Fiberwisesupports multiple database providers:
- SQLite (default):
sqlite:///~/.fiberwise/fiberwise.db
- PostgreSQL:
postgresql://user:pass@localhost/dbname
- MySQL:
mysql://user:pass@localhost/dbname
Examples
Quick Start
Initialize and start Fiberwisein development mode:
# Initialize FIberwise
fiber setup --verbose
# Start in development mode
fiber start --dev --verbose
# Create a user (optional)
fiber seed-user --username myuser --email [email protected]
Production Deployment
Set up Fiberwisefor production:
# Initialize with PostgreSQL
fiber setup --database-url "postgresql://user:pass@localhost/fiberwise" --verbose
# Start production server with worker
fiber start --port 80 --host 0.0.0.0 --worker --verbose
Agent Development
Develop and test agents:
# Activate an agent
fiber activate ./my_agent.py --verbose
# Activate with input data
fiber activate --input-data '{"prompt": "Hello, world!"}' ./chat_agent.py
# List all agents
fiber list-agents --verbose
Configuration Management
Manage multiple environments:
# Add development config
fiber account add-config --name "dev" --api-key "dev-key" --base-url "http://localhost:8000" --set-default
# Add production config
fiber account add-config --name "prod" --api-key "prod-key" --base-url "https://api.fiberwise.ai"
# List configurations
fiber account list-configs
# Add LLM provider
fiber account add-provider --provider openai --api-key YOUR_OPENAI_KEY --set-default
Application Management
Modern app lifecycle management with the restructured CLI:
# Install app from current directory (most common)
fiber app install . --verbose
# Install from specific directory to production
fiber app install /path/to/my-app --to-instance production --verbose
# Smart update (only if changes detected)
fiber app update --verbose
# Force update regardless of change detection
fiber app update --force --to-instance staging --verbose
# Install with custom manifest file
fiber app install --manifest custom_app.yaml --to-instance dev
# Multi-environment workflow
fiber app install . --to-instance dev # Development
fiber app install . --to-instance staging # Testing
fiber app install . --to-instance production # Production
# OAuth setup for apps
fiber app oauth register-authenticator --authenticator-config ./oauth/google.json
fiber app oauth list-authenticators
fiber app oauth delete-authenticator provider-id-123
Legacy vs Modern Commands
Comparison of old and new command structures:
# LEGACY (deprecated)
fiber install # Basic install
fiber install --update # Update app
fiber install --force --verbose # Force install
# MODERN (recommended)
fiber app install # Clean install
fiber app update # Smart update with change detection
fiber app install --force # Force install (if needed)
fiber app update --force # Force update
# NEW FEATURES
fiber app install --to-instance production # Instance targeting
fiber app update --verbose # Detailed progress
fiber app oauth register-authenticator --authenticator-config oauth.json # OAuth management
Function & Pipeline Management
Create, execute, and manage functions and pipelines:
# Create a simple function
echo 'def run(input_data):
name = input_data.get("name", "World")
return {"message": f"Hello, {name}!"}' > hello.py
fiber functions create hello_world \
--description "Simple greeting function" \
--type utility \
--file ./hello.py \
--verbose
# Execute the function
fiber functions execute hello_world \
--input-data '{"name": "FIberwise"}' \
--verbose
# List all functions with search
fiber functions list --search "hello" --verbose
# Show function details and history
fiber functions show hello_world --verbose
# Pipeline management
fiber functions list-pipelines
fiber functions execute-pipeline my-pipeline \
--input-data '{"input": "data"}' \
--verbose