Files
ProxmoxVE/docs/misc/build.func
CanbiZ (MickLesk) cb939861b8 github: extend docs / contribution / templates (#10921)
* Enhance setup-fork.sh with --full mode and misc/ targeting

Added a new --full flag to setup-fork.sh to allow updating all files, not just those in misc/. Updated documentation and usage examples to clarify the new behavior. Improved file search and replacement logic for broader compatibility and flexibility.

* add AI.md

* fix links in AI.md

* Update contribution docs and templates for best practices

Refreshed AI.md with new reference scripts, expanded checklist, and improved AI assistant tips. Updated container and install script templates for modern defaults (Debian 13, larger disk, two tags), clarified helper function usage, and improved update/backup patterns. Enhanced JSON template with realistic metadata, new fields, and example notes.

* Update fetch_and_deploy_gh_release usage in docs and templates

Standardize the usage of fetch_and_deploy_gh_release by specifying all arguments, including mode, version, and target directory, in AI.md and template scripts. This clarifies the function's usage and ensures consistency across documentation and install/update templates.

* Revise contribution docs and update CT template

Expanded and clarified contribution documentation for forking, local development, cherry-picking, and AI-assisted code generation. Improved explanations for setup-fork.sh, local testing, and PR submission. Enhanced the container script template with detailed comments, clearer update_script structure, and step-by-step guidance for maintainers and contributors.

* Update fork and release instructions in contribution docs

Replaced placeholder GitHub repo references with 'YourUsername/YourRepo' throughout documentation for clarity. Expanded explanations in FORK_SETUP.md and README.md to clarify the difference between development and production script execution, and emphasized the importance of cherry-picking only relevant files for PRs. Updated install script template examples to use the new repo placeholder.

* Update GitHub repo placeholders in docs and templates

Replaced 'YourUsername/YourRepo' with 'owner/repo' in documentation and template scripts for consistency and clarity. This change standardizes example usage and reduces confusion for contributors.

* Move user submitted guides to guides directory

Renamed USER_SUBMITTED_GUIDES.md from docs/contribution to docs/guides for improved documentation organization.

* Update contribution docs for improved workflow and clarity

Revised multiple documentation files to clarify the recommended development workflow: contributors must test scripts via curl from their GitHub fork (not local bash), use setup-fork.sh for URL rewriting, and submit only new files using cherry-pick. Expanded and modernized install and JSON metadata template guides, emphasizing use of helper functions, resource requirements, and the JSON generator tool. Added detailed step-by-step instructions, best practices, and updated examples throughout.

* Update contribution docs for new file structure

Updated documentation to reflect the migration of install scripts from install_scripts/ to install/, and JSON metadata from config/ to frontend/public/json/. Adjusted all relevant paths, instructions, and examples to match the new directory structure for improved clarity and consistency.

* Update contribution docs for fork setup and metadata

Revised documentation to standardize use of 'bash docs/contribution/setup-fork.sh --full' for fork configuration, clarified install script execution flow, and updated JSON metadata template and field references. Improved helper function docs, resource requirements, and category lists. Updated references and instructions throughout for consistency and accuracy.

* Docs: add GPU/TUN, update endpoints & tool refs

Documentation updates across guides and function references:

- Added var_gpu and var_tun configuration entries to CONFIGURATION_REFERENCE (GPU passthrough and TUN/TAP support), including features and prerequisites.
- Fixed repository URLs throughout UNATTENDED_DEPLOYMENTS and examples: replaced community-scripts/ProxmoxVED with community-scripts/ProxmoxVE and updated curl usage to the new paths.
- Added an "Advanced Configuration Variables" table and examples (var_os, var_version, var_gpu, var_tun, var_nesting) to UNATTENDED_DEPLOYMENTS; adjusted sample apps, hostnames, and container mappings in batch examples.
- Switched API endpoints in API_FUNCTIONS_REFERENCE and API_USAGE_EXAMPLES from http://api.community-scripts.org to https://api.community-scripts.org.
- Expanded BUILD_FUNC_FUNCTIONS_REFERENCE with container resource/ID management helper descriptions (validate_container_id, get_valid_container_id, maxkeys_check, get_current_ip, update_motd_ip).
- Large edits to TOOLS_FUNC_FUNCTIONS_REFERENCE: renamed/refactored helper signatures and docs (pkg_install -> install_packages_with_retry, pkg_update -> upgrade_packages_with_retry), added new tooling functions (fetch_and_deploy_gh_release, check_for_gh_release, prepare_repository_setup, verify_tool_version) and updated examples and feature notes.
- Updated vm/README.md to list additional VM scripts (new and reorganized examples).

These are documentation-only changes to clarify configuration options, correct links and endpoints, and expand the reference material for tooling and build helpers.

* Docs: expand developer/debugging and tools references

Add extensive documentation and examples across contribution, guides, templates and tools references. Key changes:
- Introduce a Developer Mode & Debugging section (dev_mode flags: trace, keep, pause, breakpoint, logs, dryrun, motd) in CONTRIBUTING.md with usage example.
- Provide a standard update_script() pattern and BookStack example in GUIDE.md to clarify update flow (stop services, backup, deploy, restore, migrate, restart).
- Add new helper entries (BookLore, KaraKeep) and advanced repository helpers (setup_deb822_repo, prepare_repository_setup, cleanup_tool_keyrings) plus utilities (setup_meilisearch, verify_tool_version) in HELPER_FUNCTIONS.md.
- Update install template to suggest PNPM, Java 21 and Meilisearch; update example DB setup notes in AppName-install.sh.
- Add var_diagnostics option and switch var_fuse to boolean/toggle wording in CONFIGURATION_REFERENCE.md; clarify privacy and defaults.
- Adjust example container definitions in UNATTENDED_DEPLOYMENTS.md (container entries and resource values).
- Change storage and flag variables and examples in BUILD_FUNC_USAGE_EXAMPLES.md (ssd-storage, var_fuse/var_tun, etc.).
- Expand TOOLS_FUNC_FUNCTIONS_REFERENCE.md with many setup_* function signatures, environment vars, clarified fetch_and_deploy_gh_release modes/parameters, and additional tool docs (nodejs, php, mariadb_db, postgresql_db, java, uv, yq, meilisearch, composer, build tools).

These updates improve onboarding, debugging guidance, and operational clarity for contributors and maintainers.
2026-02-05 16:45:41 +01:00
..

build.func Documentation

Overview

This directory contains comprehensive documentation for the build.func script, which is the core orchestration script for Proxmox LXC container creation in the Community Scripts project.

Documentation Files

🎛️ BUILD_FUNC_ADVANCED_SETTINGS.md

Complete reference for the 28-step Advanced Settings wizard, including all configurable options and their inheritance behavior.

Contents:

  • All 28 wizard steps explained
  • Default value inheritance
  • Feature matrix (when to enable each feature)
  • Confirmation summary format
  • Usage examples

📊 BUILD_FUNC_FLOWCHART.md

Visual ASCII flowchart showing the main execution flow, decision trees, and key decision points in the build.func script.

Contents:

  • Main execution flow diagram
  • Installation mode selection flows
  • Storage selection workflow
  • GPU passthrough decision logic
  • Variable precedence chain
  • Error handling flow
  • Integration points

🔧 BUILD_FUNC_ENVIRONMENT_VARIABLES.md

Complete reference of all environment variables used in build.func, organized by category and usage context.

Contents:

  • Core container variables
  • Operating system variables
  • Resource configuration variables
  • Network configuration variables
  • Storage configuration variables
  • Feature flags
  • GPU passthrough variables
  • API and diagnostics variables
  • Settings persistence variables
  • Variable precedence chain
  • Critical variables for non-interactive use
  • Common variable combinations

📚 BUILD_FUNC_FUNCTIONS_REFERENCE.md

Alphabetical function reference with detailed descriptions, parameters, dependencies, and usage information.

Contents:

  • Initialization functions
  • UI and menu functions
  • Storage functions
  • Container creation functions
  • GPU and hardware functions
  • Settings persistence functions
  • Utility functions
  • Function call flow
  • Function dependencies
  • Function usage examples
  • Function error handling

🔄 BUILD_FUNC_EXECUTION_FLOWS.md

Detailed execution flows for different installation modes and scenarios, including variable precedence and decision trees.

Contents:

  • Default install flow
  • Advanced install flow
  • My defaults flow
  • App defaults flow
  • Variable precedence chain
  • Storage selection logic
  • GPU passthrough flow
  • Network configuration flow
  • Container creation flow
  • Error handling flows
  • Integration flows
  • Performance considerations

🏗️ BUILD_FUNC_ARCHITECTURE.md

High-level architectural overview including module dependencies, data flow, integration points, and system architecture.

Contents:

  • High-level architecture diagram
  • Module dependencies
  • Data flow architecture
  • Integration architecture
  • System architecture components
  • User interface components
  • Security architecture
  • Performance architecture
  • Deployment architecture
  • Maintenance architecture
  • Future architecture considerations

💡 BUILD_FUNC_USAGE_EXAMPLES.md

Practical usage examples covering common scenarios, CLI examples, and environment variable combinations.

Contents:

  • Basic usage examples
  • Silent/non-interactive examples
  • Network configuration examples
  • Storage configuration examples
  • Feature configuration examples
  • Settings persistence examples
  • Error handling examples
  • Integration examples
  • Best practices

Quick Start Guide

For New Users

  1. Start with BUILD_FUNC_FLOWCHART.md to understand the overall flow
  2. Review BUILD_FUNC_ENVIRONMENT_VARIABLES.md for configuration options
  3. Follow examples in BUILD_FUNC_USAGE_EXAMPLES.md

For Developers

  1. Read BUILD_FUNC_ARCHITECTURE.md for system overview
  2. Study BUILD_FUNC_FUNCTIONS_REFERENCE.md for function details
  3. Review BUILD_FUNC_EXECUTION_FLOWS.md for implementation details

For System Administrators

  1. Focus on BUILD_FUNC_USAGE_EXAMPLES.md for deployment scenarios
  2. Review BUILD_FUNC_ENVIRONMENT_VARIABLES.md for configuration management
  3. Check BUILD_FUNC_ARCHITECTURE.md for security and performance considerations

Key Concepts

Variable Precedence

Variables are resolved in this order (highest to lowest priority):

  1. Hard environment variables (set before script execution)
  2. App-specific .vars file (/usr/local/community-scripts/defaults/<app>.vars)
  3. Global default.vars file (/usr/local/community-scripts/default.vars)
  4. Built-in defaults (set in base_settings() function)

Installation Modes

  • Default Install: Uses built-in defaults, minimal prompts
  • Advanced Install: Full interactive configuration via whiptail
  • My Defaults: Loads from global default.vars file
  • App Defaults: Loads from app-specific .vars file

Storage Selection Logic

  1. If only 1 storage exists for content type → auto-select
  2. If preselected via environment variables → validate and use
  3. Otherwise → prompt user via whiptail

GPU Passthrough Flow

  1. Detect hardware (Intel/AMD/NVIDIA)
  2. Check if app is in GPU_APPS list OR container is privileged
  3. Auto-select if single GPU type, prompt if multiple
  4. Configure /etc/pve/lxc/<ctid>.conf with proper device entries
  5. Fix GIDs post-creation to match container's video/render groups

Common Use Cases

Basic Container Creation

export APP="plex"
export CTID="100"
export var_hostname="plex-server"
export var_os="debian"
export var_version="12"
export var_cpu="4"
export var_ram="4096"
export var_disk="20"
export var_net="vmbr0"
export var_gateway="192.168.1.1"
export var_ip="192.168.1.100"
export var_template_storage="local"
export var_container_storage="local"

source build.func

GPU Passthrough

export APP="jellyfin"
export CTID="101"
export var_hostname="jellyfin-server"
export var_os="debian"
export var_version="12"
export var_cpu="8"
export var_ram="16384"
export var_disk="30"
export var_net="vmbr0"
export var_gateway="192.168.1.1"
export var_ip="192.168.1.101"
export var_template_storage="local"
export var_container_storage="local"
export GPU_APPS="jellyfin"
export var_gpu="nvidia"
export ENABLE_PRIVILEGED="true"

source build.func

Silent/Non-Interactive Deployment

#!/bin/bash
# Automated deployment
export APP="nginx"
export CTID="102"
export var_hostname="nginx-proxy"
export var_os="alpine"
export var_version="3.18"
export var_cpu="1"
export var_ram="512"
export var_disk="2"
export var_net="vmbr0"
export var_gateway="192.168.1.1"
export var_ip="192.168.1.102"
export var_template_storage="local"
export var_container_storage="local"
export ENABLE_UNPRIVILEGED="true"

source build.func

Troubleshooting

Common Issues

  1. Container creation fails: Check resource availability and configuration validity
  2. Storage errors: Verify storage exists and supports required content types
  3. Network errors: Validate network configuration and IP address availability
  4. GPU passthrough issues: Check hardware detection and container privileges
  5. Permission errors: Verify user permissions and container privileges

Debug Mode

Enable verbose output for debugging:

export VERBOSE="true"
export DIAGNOSTICS="true"
source build.func

Log Files

Check system logs for detailed error information:

  • /var/log/syslog
  • /var/log/pve/lxc/<ctid>.log
  • Container-specific logs

Contributing

When contributing to build.func documentation:

  1. Update relevant documentation files
  2. Add examples for new features
  3. Update architecture diagrams if needed
  4. Test all examples before submitting
  5. Follow the existing documentation style

Support

For issues and questions:

  1. Check this documentation first
  2. Review the troubleshooting section
  3. Check existing issues in the project repository
  4. Create a new issue with detailed information

Last updated: $(date) Documentation version: 1.0