chore(release): Update version to v1.4.298

Modernize Dockerfile with Best Practices Implementation

.vscode/settings.json

@@ -56,6 +56,7 @@
 		"godotenv",
 		"gofmt",
 		"goimports",
+		"golint",
 		"gomod",
 		"gonic",
 		"goopenai",

CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## v1.4.298 (2025-08-27)
+
+### PR [#1730](https://github.com/danielmiessler/Fabric/pull/1730) by [ksylvan](https://github.com/ksylvan): Modernize Dockerfile with Best Practices Implementation
+
+- Remove docker-test framework and simplify production docker setup by eliminating complex testing infrastructure
+- Delete entire docker-test directory including test runner scripts and environment configuration files
+- Implement multi-stage build optimization in production Dockerfile to improve build efficiency
+- Remove docker-compose.yml and start-docker.sh helper scripts to streamline container workflow
+- Update README documentation with cleaner Docker usage instructions and reduced image size benefits
+
+## v1.4.297 (2025-08-26)
+
+### PR [#1729](https://github.com/danielmiessler/Fabric/pull/1729) by [ksylvan](https://github.com/ksylvan): Add GitHub Community Health Documents
+
+- Add CODE_OF_CONDUCT defining respectful, collaborative community behavior
+- Add CONTRIBUTING with setup, testing, PR, changelog requirements
+- Add SECURITY policy with reporting process and response timelines
+- Add SUPPORT guide for bugs, features, discussions, expectations
+- Add docs README indexing guides, quick starts, contributor essentials
+
 ## v1.4.296 (2025-08-26)
 
 ### PR [#1728](https://github.com/danielmiessler/Fabric/pull/1728) by [ksylvan](https://github.com/ksylvan): Refactor Logging System to Use Centralized Debug Logger

cmd/fabric/version.go

@@ -1,3 +1,3 @@
 package main
 
-var version = "v1.4.296"
+var version = "v1.4.298"

docs/CODE_OF_CONDUCT.md

@@ -0,0 +1,26 @@
+# Code of Conduct
+
+## Our Expectation
+
+We expect all contributors and community members to act with basic human decency and common sense.
+
+This project exists to help people augment their capabilities with AI, and we welcome contributions from anyone who shares this mission. We assume good faith and trust that everyone involved is here to build something valuable together.
+
+## Guidelines
+
+- **Be respectful**: Treat others as you'd want to be treated in a professional setting
+- **Be constructive**: Focus on the work and help make the project better
+- **Be collaborative**: We're all working toward the same goal - making Fabric more useful
+- **Use good judgment**: If you're not sure whether something is appropriate, it probably isn't
+
+## Reporting Issues
+
+If someone is being genuinely disruptive or harmful, please email the maintainers directly. We'll address legitimate concerns promptly and fairly.
+
+## Enforcement
+
+Maintainers reserve the right to remove content and restrict access for anyone who consistently acts in bad faith or disrupts the community.
+
+---
+
+*This project assumes contributors are adults who can work together professionally. If you can't do that, this isn't the right place for you.*

docs/CONTRIBUTING.md

@@ -0,0 +1,155 @@
+# Contributing to Fabric
+
+Thanks for contributing to Fabric! Here's what you need to know to get started quickly.
+
+## Quick Setup
+
+### Prerequisites
+
+- Go 1.24+ installed
+- Git configured with your details
+
+### Getting Started
+
+```bash
+# Clone and setup
+git clone https://github.com/danielmiessler/fabric.git
+cd fabric
+go build -o fabric ./cmd/fabric
+./fabric --setup
+
+# Run tests
+go test ./...
+```
+
+## Development Guidelines
+
+### Code Style
+
+- Follow standard Go conventions (`gofmt`, `golint`)
+- Use meaningful variable and function names
+- Write tests for new functionality
+- Keep functions focused and small
+
+### Commit Messages
+
+Use descriptive commit messages:
+
+```text
+feat: add new pattern for code analysis
+fix: resolve OAuth token refresh issue
+docs: update installation instructions
+```
+
+### Project Structure
+
+- `cmd/` - Executable commands
+- `internal/` - Private application code
+- `data/patterns/` - AI patterns
+- `docs/` - Documentation
+
+## Pull Request Process
+
+### Changelog Generation (REQUIRED)
+
+Before submitting your PR, generate a changelog entry:
+
+```bash
+cd cmd/generate_changelog
+go build -o generate_changelog .
+./generate_changelog --incoming-pr YOUR_PR_NUMBER
+```
+
+**Requirements:**
+
+- PR must be open and mergeable
+- Working directory must be clean
+- GitHub token available (GITHUB_TOKEN env var)
+
+**Optional flags:**
+
+- `--ai-summarize` - Enhanced AI-generated summaries
+- `--push` - Auto-push the changelog commit
+
+### PR Guidelines
+
+1. Fork the repository
+2. Create a feature branch
+3. Make your changes
+4. Write/update tests
+5. Generate changelog entry (see above)
+6. Submit PR with clear description
+
+### Review Process
+
+- PRs require maintainer review
+- Address feedback promptly
+- Keep PRs focused on single features/fixes
+- Update changelog if you make significant changes
+
+## Testing
+
+### Run Tests
+
+```bash
+# All tests
+go test ./...
+
+# Specific package
+go test ./internal/cli
+
+# With coverage
+go test -cover ./...
+```
+
+### Test Requirements
+
+- Unit tests for core functionality
+- Integration tests for external dependencies
+- Examples in documentation
+
+## Patterns
+
+### Creating Patterns
+
+Patterns go in `data/patterns/[pattern-name]/system.md`:
+
+```markdown
+# IDENTITY and PURPOSE
+You are an expert at...
+
+# STEPS
+- Step 1
+- Step 2
+
+# OUTPUT
+- Output format requirements
+
+# EXAMPLE
+Example output here
+```
+
+### Pattern Guidelines
+
+- Use clear, actionable language
+- Provide specific output formats
+- Include examples when helpful
+- Test with multiple AI providers
+
+## Documentation
+
+- Update README.md for new features
+- Add docs to `docs/` for complex features
+- Include usage examples
+- Keep documentation current
+
+## Getting Help
+
+- Check existing issues first
+- Ask questions in discussions
+- Tag maintainers for urgent issues
+- Be patient - maintainers are volunteers
+
+## License
+
+By contributing, you agree your contributions will be licensed under the MIT License.

docs/README.md

@@ -0,0 +1,88 @@
+# Fabric Documentation
+
+Welcome to the Fabric documentation! This directory contains detailed guides and technical documentation for various features and components of Fabric.
+
+## 📚 Available Documentation
+
+### Core Features
+
+**[Automated-Changelog-Usage.md](./Automated-Changelog-Usage.md)**
+Complete guide for developers on using the automated changelog system. Covers the workflow for generating PR changelog entries during development, including setup, validation, and CI/CD integration.
+
+**[YouTube-Processing.md](./YouTube-Processing.md)**
+Comprehensive guide for processing YouTube videos and playlists with Fabric. Covers transcript extraction, comment processing, metadata retrieval, and advanced yt-dlp configurations.
+
+**[Using-Speech-To-Text.md](./Using-Speech-To-Text.md)**
+Documentation for Fabric's speech-to-text capabilities using OpenAI's Whisper models. Learn how to transcribe audio and video files and process them through Fabric patterns.
+
+### User Interface & Experience
+
+**[Desktop-Notifications.md](./Desktop-Notifications.md)**
+Guide to setting up desktop notifications for Fabric commands. Useful for long-running tasks and multitasking scenarios with cross-platform notification support.
+
+**[Shell-Completions.md](./Shell-Completions.md)**
+Instructions for setting up intelligent tab completion for Fabric in Zsh, Bash, and Fish shells. Includes automated installation and manual setup options.
+
+**[Gemini-TTS.md](./Gemini-TTS.md)**
+Complete guide for using Google Gemini's text-to-speech features with Fabric. Covers voice selection, audio generation, and integration with Fabric patterns.
+
+### Development & Architecture
+
+**[Automated-ChangeLog.md](./Automated-ChangeLog.md)**
+Technical documentation outlining the automated CHANGELOG system architecture for CI/CD integration. Details the infrastructure and workflow for maintainers.
+
+**[Project-Restructured.md](./Project-Restructured.md)**
+Project restructuring plan and architectural decisions. Documents the transition to standard Go conventions and project organization improvements.
+
+**[NOTES.md](./NOTES.md)**
+Development notes on refactoring efforts, model management improvements, and architectural changes. Includes technical details on vendor and model abstraction.
+
+### Audio Resources
+
+**[voices/README.md](./voices/README.md)**
+Index of Gemini TTS voice samples demonstrating different AI voice characteristics available in Fabric.
+
+## 🗂️ Additional Resources
+
+### Configuration Files
+
+- `./notification-config.yaml` - Example notification configuration
+
+### Images
+
+- `images/` - Screenshots and visual documentation assets
+  - `fabric-logo-gif.gif` - Animated Fabric logo
+  - `fabric-summarize.png` - Screenshot of summarization feature
+  - `svelte-preview.png` - Web interface preview
+
+## 🚀 Quick Start
+
+New to Fabric? Start with these essential docs:
+
+1. **[../README.md](../README.md)** - Main project README with installation and basic usage
+2. **[Shell-Completions.md](./Shell-Completions.md)** - Set up tab completion for better CLI experience
+3. **[YouTube-Processing.md](./YouTube-Processing.md)** - Learn one of Fabric's most popular features
+4. **[Desktop-Notifications.md](./Desktop-Notifications.md)** - Get notified when long tasks complete
+
+## 🔧 For Contributors
+
+Contributing to Fabric? These docs are essential:
+
+1. **[./CONTRIBUTING.md](./CONTRIBUTING.md)** - Contribution guidelines and setup
+2. **[Automated-Changelog-Usage.md](./Automated-Changelog-Usage.md)** - Required workflow for PR submissions
+3. **[Project-Restructured.md](./Project-Restructured.md)** - Understanding project architecture
+4. **[NOTES.md](./NOTES.md)** - Current development priorities and patterns
+
+## 📝 Documentation Standards
+
+When adding new documentation:
+
+- Use clear, descriptive filenames
+- Include practical examples and use cases
+- Update this README index with your new docs
+- Follow the established markdown formatting conventions
+- Test all code examples before publication
+
+---
+
+*For general help and support, see [./SUPPORT.md](./SUPPORT.md)*

docs/SECURITY.md

@@ -0,0 +1,158 @@
+# Security Policy
+
+## Supported Versions
+
+We aim to provide security updates for the latest version of Fabric.
+
+We recommend always using the latest version of Fabric for security fixes and improvements.
+
+## Reporting Security Vulnerabilities
+
+**Please DO NOT report security vulnerabilities through public GitHub issues.**
+
+### Preferred Reporting Method
+
+Send security reports directly to: **<kayvan@sylvan.com>** and CC to the project maintainer at **<daniel@danielmiessler.com>**
+
+### What to Include
+
+Please provide the following information:
+
+1. **Vulnerability Type**: What kind of security issue (e.g., injection, authentication bypass, etc.)
+2. **Affected Components**: Which parts of Fabric are affected
+3. **Impact Assessment**: What could an attacker accomplish
+4. **Reproduction Steps**: Clear steps to reproduce the vulnerability
+5. **Proposed Fix**: If you have suggestions for remediation
+6. **Disclosure Timeline**: Your preferred timeline for public disclosure
+
+### Example Report Format
+
+```text
+Subject: [SECURITY] Brief description of vulnerability
+
+Vulnerability Type: SQL Injection
+Affected Component: Pattern database queries
+Impact: Potential data exposure
+Severity: High
+
+Reproduction Steps:
+1. Navigate to...
+2. Submit payload: ...
+3. Observe...
+
+Evidence:
+[Screenshots, logs, or proof of concept]
+
+Suggested Fix:
+Use parameterized queries instead of string concatenation...
+```
+
+## Security Considerations
+
+### API Keys and Secrets
+
+- Never commit API keys to the repository
+- Store secrets in environment variables or secure configuration
+- Use the built-in setup process for key management
+- Regularly rotate API keys
+
+### Input Validation
+
+- All user inputs are validated before processing
+- Special attention to pattern definitions and user content
+- URL validation for web scraping features
+
+### AI Provider Integration
+
+- Secure communication with AI providers (HTTPS/TLS)
+- Token handling follows provider best practices
+- No sensitive data logged or cached unencrypted
+
+### Network Security
+
+- Web server endpoints properly authenticated when required
+- CORS policies appropriately configured
+- Rate limiting implemented where necessary
+
+## Vulnerability Response Process
+
+1. **Report Received**: We'll acknowledge receipt within 24 hours
+2. **Initial Assessment**: We'll evaluate severity and impact within 72 hours
+3. **Investigation**: We'll investigate and develop fixes
+4. **Fix Development**: We'll create and test patches
+5. **Coordinated Disclosure**: We'll work with reporter on disclosure timeline
+6. **Release**: We'll release patched version with security advisory
+
+### Timeline Expectations
+
+- **Critical**: 1-7 days
+- **High**: 7-30 days
+- **Medium**: 30-90 days
+- **Low**: Next scheduled release
+
+## Bug Bounty
+
+We don't currently offer a formal bug bounty program, but we deeply appreciate security research and will:
+
+- Acknowledge contributors in release notes
+- Provide credit in security advisories
+- Consider swag or small rewards for significant findings
+
+## Security Best Practices for Users
+
+### Installation
+
+- Download Fabric only from official sources
+- Verify checksums when available
+- Keep installations up to date
+
+### Configuration
+
+- Use strong, unique API keys
+- Don't share configuration files containing secrets
+- Set appropriate file permissions on config directories
+
+### Usage
+
+- Be cautious with patterns that process sensitive data
+- Review AI provider terms for data handling
+- Consider using local models for sensitive content
+
+## Known Security Limitations
+
+### AI Provider Dependencies
+
+Fabric relies on external AI providers. Security depends partly on:
+
+- Provider security practices
+- Data transmission security
+- Provider data handling policies
+
+### Pattern Execution
+
+Custom patterns could potentially:
+
+- Process sensitive inputs inappropriately
+- Generate outputs containing sensitive information
+- Be used for adversarial prompt injection
+
+**Recommendation**: Review patterns carefully, especially those from untrusted sources.
+
+## Security Updates
+
+Security updates are distributed through:
+
+- GitHub Releases with security tags
+- Security advisories on GitHub
+- Project documentation updates
+
+Subscribe to the repository to receive notifications about security updates.
+
+## Contact
+
+For non-security issues, please use GitHub issues.
+For security concerns, email: **<kayvan@sylvan.com>** and CC to **<daniel@danielmiessler.com>**
+
+---
+
+*We take security seriously and appreciate the security research community's help in keeping Fabric secure.*

docs/SUPPORT.md

@@ -0,0 +1,148 @@
+# Support
+
+## Getting Help with Fabric
+
+Need help with Fabric? Here are the best ways to get assistance:
+
+## 📖 Documentation First
+
+Before reaching out, check these resources:
+
+- **[README.md](../README.md)** - Installation, usage, and examples
+- **[docs/](./README.md)** - Detailed documentation
+- **[Patterns](../data/patterns/)** - Browse available AI patterns
+
+## 🐛 Bug Reports
+
+Found a bug? Please create an issue:
+
+**[Report a Bug](https://github.com/danielmiessler/fabric/issues/new?template=bug.yml)**
+
+Include:
+
+- Fabric version (`fabric --version`)
+- Operating system
+- Steps to reproduce
+- Expected vs actual behavior
+- Error messages/logs
+
+## 💡 Feature Requests
+
+Have an idea for Fabric? We'd love to hear it:
+
+**[Request a Feature](https://github.com/danielmiessler/fabric/issues/new)**
+
+Describe:
+
+- What you want to achieve
+- Why it would be useful
+- How you envision it working
+- Any alternatives you've considered
+
+## 🤔 Questions & Discussions
+
+For general questions, usage help, or community discussion:
+
+**[GitHub Discussions](https://github.com/danielmiessler/fabric/discussions)**
+
+Great for:
+
+- "How do I...?" questions
+- Sharing patterns you've created
+- Getting community advice
+- Feature brainstorming
+
+## 🏷️ Issue Labels
+
+When creating issues, maintainers will add appropriate labels:
+
+- `bug` - Something isn't working
+- `enhancement` - New feature request
+- `documentation` - Documentation improvements
+- `help wanted` - Community contributions welcome
+- `good first issue` - Great for new contributors
+- `question` - General questions
+- `pattern` - Related to AI patterns
+
+## 📋 Issue Templates
+
+We provide templates to help you create detailed reports:
+
+- **Bug Report** - Structured bug reporting
+- **Feature Request** - Detailed feature proposals
+- **Pattern Submission** - New pattern contributions
+
+## 🔒 Security Issues
+
+**DO NOT create public issues for security vulnerabilities.**
+
+See our [Security Policy](./SECURITY.md) for proper reporting procedures.
+
+## ⚡ Response Times
+
+We're a community-driven project with volunteer maintainers:
+
+- **Bugs**: We aim to acknowledge within 48 hours
+- **Features**: Response time varies based on complexity
+- **Questions**: Community often responds quickly
+- **Security**: See security policy for timelines
+
+## 🛠️ Self-Help Tips
+
+Before creating an issue, try:
+
+1. **Update Fabric**: `go install github.com/danielmiessler/fabric/cmd/fabric@latest`
+2. **Check existing issues**: Someone might have the same problem
+3. **Run setup**: `fabric --setup` can fix configuration issues
+4. **Test minimal example**: Isolate the problem
+
+## 🤝 Community Guidelines
+
+When asking for help:
+
+- Be specific and provide context
+- Include relevant details and error messages
+- Be patient - maintainers are volunteers
+- Help others when you can
+- Say thanks when someone helps you
+
+## 📞 Emergency Contact
+
+For urgent security issues only:
+
+- Email: <security@fabric.ai> (if available)
+- Maintainer: <daniel@danielmiessler.com>
+
+## 🎯 What We Can Help With
+
+✅ **We can help with:**
+
+- Installation and setup issues
+- Usage questions and examples
+- Bug reports and fixes
+- Feature discussions
+- Pattern creation guidance
+- Integration questions
+
+❌ **We cannot help with:**
+
+- Custom development for your specific use case
+- Troubleshooting your specific AI provider issues
+- General AI or programming tutorials
+- Commercial support agreements
+
+## 💪 Contributing Back
+
+The best way to get help is to help others:
+
+- Answer questions in discussions
+- Improve documentation
+- Share useful patterns
+- Report bugs clearly
+- Review pull requests
+
+See our [Contributing Guide](./CONTRIBUTING.md) for details.
+
+---
+
+*Remember: We're all here to make Fabric better. Be kind, be helpful, and let's build something amazing together!*

nix/pkgs/fabric/version.nix

@@ -1 +1 @@
-"1.4.296"
+"1.4.298"

scripts/docker-test/README.md

@@ -1,116 +0,0 @@
-# Docker Test Environment for API Configuration Fix
-
-This directory contains a Docker-based testing setup for fixing the issue where Fabric calls Ollama and Bedrock APIs even when not configured. This addresses the problem where unconfigured services show error messages during model listing.
-
-## Quick Start
-
-```bash
-# Run all tests
-./scripts/docker-test/test-runner.sh
-
-# Interactive mode - pick which test to run
-./scripts/docker-test/test-runner.sh -i
-
-# Run specific test case
-./scripts/docker-test/test-runner.sh gemini-only
-
-# Shell into test environment
-./scripts/docker-test/test-runner.sh -s gemini-only
-
-# Build image only (for development)
-./scripts/docker-test/test-runner.sh -b
-
-# Show help
-./scripts/docker-test/test-runner.sh -h
-```
-
-## Test Cases
-
-1. **no-config**: No APIs configured
-2. **gemini-only**: Only Gemini configured (reproduces original issue #1195)
-3. **openai-only**: Only OpenAI configured
-4. **ollama-only**: Only Ollama configured
-5. **bedrock-only**: Only Bedrock configured
-6. **mixed**: Multiple APIs configured (Gemini + OpenAI + Ollama)
-
-## Environment Files
-
-Each test case has a corresponding environment file in `scripts/docker-test/env/`:
-
-- `env.no-config` - Empty configuration
-- `env.gemini-only` - Only Gemini API key
-- `env.openai-only` - Only OpenAI API key
-- `env.ollama-only` - Only Ollama URL
-- `env.bedrock-only` - Only Bedrock configuration
-- `env.mixed` - Multiple API configurations
-
-These files are volume-mounted into the Docker container and persist changes made with `fabric -S`.
-
-## Interactive Mode & Shell Access
-
-The interactive mode (`-i`) provides several options:
-
-```text
-Available test cases:
-
-1) No APIs configured (no-config)
-2) Only Gemini configured (gemini-only)
-3) Only OpenAI configured (openai-only)
-4) Only Ollama configured (ollama-only)
-5) Only Bedrock configured (bedrock-only)
-6) Mixed configuration (mixed)
-7) Run all tests
-0) Exit
-
-Add '!' after number to shell into test environment (e.g., '1!' to shell into no-config)
-```
-
-### Shell Mode
-
-- Use `1!`, `2!`, etc. to shell into any test environment
-- Run `fabric -S` to configure APIs interactively
-- Run `fabric --listmodels` or `fabric -L` to test model listing
-- Changes persist in the environment files
-- Type `exit` to return to test runner
-
-## Expected Results
-
-**Before Fix:**
-
-- `no-config` and `gemini-only` tests show Ollama connection errors
-- Tests show Bedrock authentication errors when BEDROCK_AWS_REGION not set
-- Error: `Ollama Get "http://localhost:11434/api/tags": dial tcp...`
-- Error: `Bedrock failed to list foundation models...`
-
-**After Fix:**
-
-- Clean output with no error messages for unconfigured services
-- Only configured services appear in model listings
-- Ollama only initialized when `OLLAMA_API_URL` is set
-- Bedrock only initialized when `BEDROCK_AWS_REGION` is set
-
-## Implementation Details
-
-- **Volume-mounted configs**: Environment files are mounted to `/home/testuser/.config/fabric/.env`
-- **Persistent state**: Configuration changes survive between test runs
-- **Single Docker image**: Built once from `scripts/docker-test/base/Dockerfile`, reused for all tests
-- **Isolated environments**: Each test uses its own environment file
-- **Cross-platform**: Works on macOS, Linux, and Windows with Docker
-
-## Development Workflow
-
-1. Make code changes to fix API initialization logic
-2. Run `./scripts/docker-test/test-runner.sh no-config` to test the main issue
-3. Use `./scripts/docker-test/test-runner.sh -i` for interactive testing
-4. Shell into environments (`1!`, `2!`, etc.) to debug specific configurations
-5. Run all tests before submitting PR: `./scripts/docker-test/test-runner.sh`
-
-## Architecture
-
-The fix involves:
-
-1. **Ollama**: Override `IsConfigured()` method to check for `OLLAMA_API_URL` env var
-2. **Bedrock**: Modify `hasAWSCredentials()` to require `BEDROCK_AWS_REGION`
-3. **Plugin Registry**: Only initialize providers when properly configured
-
-This prevents unnecessary API calls and eliminates confusing error messages for users.

scripts/docker-test/base/Dockerfile

@@ -1,30 +0,0 @@
-FROM golang:1.24-alpine AS builder
-
-WORKDIR /app
-COPY go.mod go.sum ./
-RUN go mod download
-
-COPY ./cmd/fabric ./cmd/fabric
-COPY ./internal ./internal
-RUN go build -o fabric ./cmd/fabric
-
-FROM alpine:latest
-RUN apk --no-cache add ca-certificates
-
-# Create a test user
-RUN adduser -D -s /bin/sh testuser
-
-# Switch to test user
-USER testuser
-WORKDIR /home/testuser
-
-# Set environment variables for the test user
-ENV HOME=/home/testuser
-ENV USER=testuser
-
-COPY --from=builder /app/fabric .
-
-# Create fabric config directory and empty .env file
-RUN mkdir -p .config/fabric && touch .config/fabric/.env
-
-ENTRYPOINT ["./fabric"]

scripts/docker-test/test-runner.sh

@@ -1,235 +0,0 @@
-#!/usr/bin/env bash
-
-set -e
-
-# Get the directory where this script is located
-top_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-base_name="$(basename "$top_dir")"
-cd "$top_dir"/../.. || exit 1
-
-# Check if bash version supports associative arrays
-if [[ ${BASH_VERSION%%.*} -lt 4 ]]; then
-    echo "This script requires bash 4.0 or later for associative arrays."
-    echo "Current version: $BASH_VERSION"
-    exit 1
-fi
-
-IMAGE_NAME="fabric-test-setup"
-ENV_DIR="scripts/${base_name}/env"
-
-# Test case descriptions
-declare -A test_descriptions=(
-    ["no-config"]="No APIs configured"
-    ["gemini-only"]="Only Gemini configured (reproduces original issue)"
-    ["openai-only"]="Only OpenAI configured"
-    ["ollama-only"]="Only Ollama configured"
-    ["bedrock-only"]="Only Bedrock configured"
-    ["mixed"]="Mixed configuration (Gemini + OpenAI + Ollama)"
-)
-
-# Test case order for consistent display
-test_order=("no-config" "gemini-only" "openai-only" "ollama-only" "bedrock-only" "mixed")
-
-build_image() {
-    echo "=== Building Docker image ==="
-    docker build -f "${top_dir}/base/Dockerfile" -t "$IMAGE_NAME" .
-    echo
-}
-
-check_env_file() {
-    local test_name="$1"
-    local env_file="$ENV_DIR/env.$test_name"
-
-    if [[ ! -f "$env_file" ]]; then
-        echo "Error: Environment file not found: $env_file"
-        exit 1
-    fi
-}
-
-run_test() {
-    local test_name="$1"
-    local description="${test_descriptions[$test_name]}"
-    local env_file="$ENV_DIR/env.$test_name"
-
-    check_env_file "$test_name"
-
-    echo "===================="
-    echo "Test: $description"
-    echo "Config: $test_name"
-    echo "Env file: $env_file"
-    echo "===================="
-
-    echo "Running test..."
-    if docker run --rm \
-        -e HOME=/home/testuser \
-        -e USER=testuser \
-        -v "$(pwd)/$env_file:/home/testuser/.config/fabric/.env:ro" \
-        "$IMAGE_NAME" --listmodels 2>&1; then
-        echo "✅ Test completed"
-    else
-        echo "❌ Test failed"
-    fi
-    echo
-}
-
-shell_into_env() {
-    local test_name="$1"
-    local description="${test_descriptions[$test_name]}"
-    local env_file="$ENV_DIR/env.$test_name"
-
-    check_env_file "$test_name"
-
-    echo "===================="
-    echo "Shelling into: $description"
-    echo "Config: $test_name"
-    echo "Env file: $env_file"
-    echo "===================="
-    echo "You can now run 'fabric -S' to configure, or 'fabric --listmodels' or 'fabric -L' to test."
-    echo "Changes to .env will persist in $env_file"
-    echo "Type 'exit' to return to the test runner."
-    echo
-
-    docker run -it --rm \
-        -e HOME=/home/testuser \
-        -e USER=testuser \
-        -v "$(pwd)/$env_file:/home/testuser/.config/fabric/.env" \
-        --entrypoint=/bin/sh \
-        "$IMAGE_NAME"
-}
-
-interactive_mode() {
-    echo "=== Interactive Mode ==="
-    echo "Available test cases:"
-    echo
-    local i=1
-    local cases=()
-    for test_name in "${test_order[@]}"; do
-        echo "$i) ${test_descriptions[$test_name]} ($test_name)"
-        cases[i]="$test_name"
-        ((i++))
-    done
-    echo "$i) Run all tests"
-    echo "0) Exit"
-    echo
-    echo "Add '!' after number to shell into test environment (e.g., '1!' to shell into no-config)"
-    echo
-
-    while true; do
-        read -r -p "Select test case (0-$i) [or 1!, etc. to shell into test environment]: " choice
-
-        # Check for shell mode (! suffix)
-        local shell_mode=false
-        if [[ "$choice" == *"!" ]]; then
-            shell_mode=true
-            choice="${choice%!}"  # Remove the ! suffix
-        fi
-
-        if [[ "$choice" == "0" ]]; then
-            if [[ "$shell_mode" == true ]]; then
-                echo "Cannot shell into exit option."
-                continue
-            fi
-            echo "Exiting..."
-            exit 0
-        elif [[ "$choice" == "$i" ]]; then
-            if [[ "$shell_mode" == true ]]; then
-                echo "Cannot shell into 'run all tests' option."
-                continue
-            fi
-            echo "Running all tests..."
-            run_all_tests
-            break
-        elif [[ "$choice" -ge 1 && "$choice" -lt "$i" ]]; then
-            local selected_test="${cases[$choice]}"
-            if [[ "$shell_mode" == true ]]; then
-                echo "Shelling into: ${test_descriptions[$selected_test]}"
-                shell_into_env "$selected_test"
-            else
-                echo "Running: ${test_descriptions[$selected_test]}"
-                run_test "$selected_test"
-            fi
-
-            read -r -p "Continue testing? (y/n): " again
-            if [[ "$again" != "y" && "$again" != "Y" ]]; then
-                break
-            fi
-            echo
-        else
-            echo "Invalid choice. Please select 0-$i (optionally with '!' for shell mode)."
-        fi
-    done
-}
-
-run_all_tests() {
-    echo "=== Testing PR #1645: Conditional API initialization ==="
-    echo
-
-    for test_name in "${test_order[@]}"; do
-        run_test "$test_name"
-    done
-
-    echo "=== Test run complete ==="
-    echo "Review the output above to check:"
-    echo "1. No Ollama connection errors when OLLAMA_URL not set"
-    echo "2. No Bedrock authentication errors when BEDROCK_AWS_REGION not set"
-    echo "3. Only configured services appear in model listings"
-}
-
-show_help() {
-    echo "Usage: $0 [OPTIONS] [TEST_CASE]"
-    echo
-    echo "Test PR #1645 conditional API initialization"
-    echo
-    echo "Options:"
-    echo "  -h, --help       Show this help message"
-    echo "  -i, --interactive Run in interactive mode"
-    echo "  -b, --build-only  Build image only, don't run tests"
-    echo "  -s, --shell TEST  Shell into test environment"
-    echo
-    echo "Test cases:"
-    for test_name in "${test_order[@]}"; do
-        echo "  $test_name: ${test_descriptions[$test_name]}"
-    done
-    echo
-    echo "Examples:"
-    echo "  $0                    # Run all tests"
-    echo "  $0 -i                 # Interactive mode"
-    echo "  $0 gemini-only        # Run specific test"
-    echo "  $0 -s gemini-only     # Shell into gemini-only environment"
-    echo "  $0 -b                 # Build image only"
-    echo
-    echo "Environment files are located in $ENV_DIR/ and can be edited directly."
-}
-
-# Parse command line arguments
-if [[ $# -eq 0 ]]; then
-    build_image
-    run_all_tests
-elif [[ "$1" == "-h" || "$1" == "--help" ]]; then
-    show_help
-elif [[ "$1" == "-i" || "$1" == "--interactive" ]]; then
-    build_image
-    interactive_mode
-elif [[ "$1" == "-b" || "$1" == "--build-only" ]]; then
-    build_image
-elif [[ "$1" == "-s" || "$1" == "--shell" ]]; then
-    if [[ -z "$2" ]]; then
-        echo "Error: -s/--shell requires a test case name"
-        echo "Use -h for help."
-        exit 1
-    fi
-    if [[ -z "${test_descriptions[$2]}" ]]; then
-        echo "Error: Unknown test case: $2"
-        echo "Use -h for help."
-        exit 1
-    fi
-    build_image
-    shell_into_env "$2"
-elif [[ -n "${test_descriptions[$1]}" ]]; then
-    build_image
-    run_test "$1"
-else
-    echo "Unknown test case or option: $1"
-    echo "Use -h for help."
-    exit 1
-fi

scripts/docker/Dockerfile

@@ -1,41 +1,26 @@
-# Use official golang image as builder
-FROM golang:1.24.2-alpine AS builder
+# syntax=docker/dockerfile:1
 
-# Set working directory
-WORKDIR /app
+FROM golang:1.24-alpine AS builder
+
+WORKDIR /src
+
+# Install build dependencies
+RUN apk add --no-cache git
 
-# Copy go mod and sum files
 COPY go.mod go.sum ./
-
-# Download dependencies
 RUN go mod download
 
-# Copy source code
 COPY . .
 
-# Build the application
-RUN CGO_ENABLED=0 GOOS=linux go build -o fabric ./cmd/fabric
+RUN CGO_ENABLED=0 GOOS=linux go build -ldflags="-s -w" -o /fabric ./cmd/fabric
 
-# Use scratch as final base image
 FROM alpine:latest
 
-# Copy the binary from builder
-COPY --from=builder /app/fabric /fabric
+RUN apk add --no-cache ca-certificates \
+    && mkdir -p /root/.config/fabric
 
-# Copy patterns directory
-COPY patterns /patterns
+COPY --from=builder /fabric /usr/local/bin/fabric
 
-# Ensure clean config directory and copy ENV file
-RUN rm -rf /root/.config/fabric && \
-    mkdir -p /root/.config/fabric
-COPY ENV /root/.config/fabric/.env
-
-# Add debug commands
-RUN ls -la /root/.config/fabric/
-
-# Expose port 8080
 EXPOSE 8080
 
-# Run the binary with debug output
-ENTRYPOINT ["/fabric"]
-CMD ["--serve"] 
+ENTRYPOINT ["fabric"]

scripts/docker/README.md

@@ -1,40 +1,48 @@
-# Docker Deployment
+# Fabric Docker Image
 
-This directory contains Docker configuration files for running Fabric in containers.
+This directory provides a simple Docker setup for running the [Fabric](https://github.com/danielmiessler/fabric) CLI.
 
-## Files
+## Build
 
-- `Dockerfile` - Main Docker build configuration
-- `docker-compose.yml` - Docker Compose stack configuration  
-- `start-docker.sh` - Helper script to start the stack
-- `README.md` - This documentation
-
-## Quick Start
+Build the image from the repository root:
 
 ```bash
-# Start the Docker stack
-./start-docker.sh
-
-# Or manually with docker-compose
-docker-compose up -d
-
-# View logs
-docker-compose logs -f
-
-# Stop the stack
-docker-compose down
+docker build -t fabric -f scripts/docker/Dockerfile .
 ```
 
-## Building
+## Persisting configuration
+
+Fabric stores its configuration in `~/.config/fabric/.env`. Mount this path to keep your settings on the host.
+
+### Using a host directory
 
 ```bash
-# Build the Docker image
-docker build -t fabric .
-
-# Or use docker-compose
-docker-compose build
+mkdir -p $HOME/.fabric-config
+# Run setup to create the .env and download patterns
+ docker run --rm -it -v $HOME/.fabric-config:/root/.config/fabric fabric --setup
 ```
 
-## Configuration
+Subsequent runs can reuse the same directory:
 
-Make sure to configure your environment variables and API keys before running the Docker stack. See the main README.md for setup instructions.
+```bash
+docker run --rm -it -v $HOME/.fabric-config:/root/.config/fabric fabric -p your-pattern
+```
+
+### Mounting a single .env file
+
+If you only want to persist the `.env` file:
+
+```bash
+# assuming .env exists in the current directory
+docker run --rm -it -v $PWD/.env:/root/.config/fabric/.env fabric -p your-pattern
+```
+
+## Running the server
+
+Expose port 8080 to use Fabric's REST API:
+
+```bash
+docker run --rm -it -p 8080:8080 -v $HOME/.fabric-config:/root/.config/fabric fabric --serve
+```
+
+The API will be available at `http://localhost:8080`.

scripts/docker/docker-compose.yml

@@ -1,11 +0,0 @@
-version: '3.8'
-
-services:
-  fabric-api:
-    build: .
-    ports:
-      - "8080:8080"
-    volumes:
-      - ./ENV:/root/.config/fabric/.env:ro
-    environment:
-      - GIN_MODE=release 

scripts/docker/start-docker.sh

@@ -1,11 +0,0 @@
-#!/bin/bash
-
-# Helper script to start the Fabric Docker stack
-
-echo "Starting Fabric Docker stack..."
-cd "$(dirname "$0")"
-docker-compose up -d
-
-echo "Fabric is now running!"
-echo "Check logs with: docker-compose logs -f"
-echo "Stop with: docker-compose down"