Delete teleport (ct) after migration to ProxmoxVE

.github/workflows/move-to-main-repo.yaml

@@ -39,22 +39,11 @@ jobs:
         env:
           GH_TOKEN: ${{ github.token }}
         run: |
-          echo "Resolving issue with label Migration To ProxmoxVE"
+          echo "Filtering Issues with Label Migration To ProxmoxVE"
+          raw_output=$(gh issue list --json title,labels,number,body)
+          filtered_issue=$(echo "$raw_output" | jq -r '[.[] | select(.labels[]?.name == "Migration To ProxmoxVE")][0]')
 
-          if [[ "${{ github.event_name }}" == "issues" ]]; then
-            # For labeled issue events, use the exact issue from event payload.
-            filtered_issue='${{ toJson(github.event.issue) }}'
-          else
-            # Fallback for workflow_dispatch: query explicitly by label and raise limit.
-            raw_output=$(gh issue list \
-              --label "Migration To ProxmoxVE" \
-              --state open \
-              --limit 500 \
-              --json title,labels,number,body)
-            filtered_issue=$(echo "$raw_output" | jq -c '.[0]')
-          fi
-
-          if [[ "$filtered_issue" == "null" ]] || [[ -z "$filtered_issue" ]]; then
+          if [ "$filtered_issue" == "null" ] || [ -z "$filtered_issue" ]; then
             echo "No issues found with label 'Migration To ProxmoxVE'."
             exit 1
           fi

.github/workflows/push_json_to_pocketbase.yml

@@ -1,11 +1,6 @@
 name: Push JSON changes to PocketBase
 
 on:
-  push:
-    branches:
-      - main
-    paths:
-      - "json/*.json"
   workflow_dispatch:
     inputs:
       script_slug:
@@ -25,52 +20,20 @@ jobs:
       - name: Get JSON file for script
         id: changed
         run: |
-          : > changed_app_jsons.txt
-
-          if [[ "${{ github.event_name }}" == "workflow_dispatch" ]]; then
-            script_slug="${{ github.event.inputs.script_slug }}"
-            file="json/${script_slug}.json"
-            if [[ ! -f "$file" ]]; then
-              echo "No JSON file at $file."
-              echo "count=0" >> "$GITHUB_OUTPUT"
-              exit 0
-            fi
-            if ! jq -e '.slug' "$file" >/dev/null 2>&1; then
-              echo "File $file has no .slug."
-              echo "count=0" >> "$GITHUB_OUTPUT"
-              exit 0
-            fi
-            echo "$file" > changed_app_jsons.txt
-            echo "count=1" >> "$GITHUB_OUTPUT"
-            exit 0
-          fi
-
-          changed=$(git diff --name-only "${{ github.event.before }}" "${{ github.event.after }}" -- json/*.json || true)
-          if [[ -z "$changed" ]]; then
-            echo "No JSON files changed under json/*.json."
+          script_slug="${{ github.event.inputs.script_slug }}"
+          file="json/${script_slug}.json"
+          if [[ ! -f "$file" ]]; then
+            echo "No JSON file at $file."
             echo "count=0" >> "$GITHUB_OUTPUT"
             exit 0
           fi
-
-          count=0
-          for file in $changed; do
-            [[ -f "$file" ]] || continue
-            if [[ "$file" == "json/metadata.json" || "$file" == "json/update-apps.json" || "$file" == "json/versions.json" ]]; then
-              continue
-            fi
-            if jq -e '.slug' "$file" >/dev/null 2>&1; then
-              echo "$file" >> changed_app_jsons.txt
-              count=$((count + 1))
-            fi
-          done
-
-          if [[ $count -eq 0 ]]; then
-            echo "No app JSON files with .slug found in this push."
+          if ! jq -e '.slug' "$file" >/dev/null 2>&1; then
+            echo "File $file has no .slug."
             echo "count=0" >> "$GITHUB_OUTPUT"
             exit 0
           fi
-
-          echo "count=$count" >> "$GITHUB_OUTPUT"
+          echo "$file" > changed_app_jsons.txt
+          echo "count=1" >> "$GITHUB_OUTPUT"
 
       - name: Push to PocketBase
         if: steps.changed.outputs.count != '0'

ct/alpine-wakapi.sh

@@ -0,0 +1,75 @@
+#!/usr/bin/env bash
+source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/misc/build.func)
+
+# Copyright (c) 2021-2026 community-scripts ORG
+# Author: Slaviša Arežina (tremor021)
+# License: MIT | https://github.com/community-scripts/ProxmoxVED/raw/main/LICENSE
+# Source: https://wakapi.dev/ | https://github.com/muety/wakapi
+
+APP="Alpine-Wakapi"
+var_tags="${var_tags:-code;time-tracking}"
+var_cpu="${var_cpu:-1}"
+var_ram="${var_ram:-512}"
+var_disk="${var_disk:-4}"
+var_os="${var_os:-alpine}"
+var_version="${var_version:-3.23}"
+var_unprivileged="${var_unprivileged:-1}"
+
+header_info "$APP"
+variables
+color
+catch_errors
+
+function update_script() {
+  header_info
+  check_container_storage
+  check_container_resources
+  if [[ ! -d /opt/wakapi ]]; then
+    msg_error "No ${APP} Installation Found!"
+    exit
+  fi
+
+  RELEASE=$(curl -s https://api.github.com/repos/muety/wakapi/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')
+  if [ "${RELEASE}" != "$(cat ~/.wakapi 2>/dev/null)" ] || [ ! -f ~/.wakapi ]; then
+    msg_info "Stopping Wakapi Service"
+    $STD rc-service wakapi stop
+    msg_ok "Stopped Wakapi Service"
+
+    msg_info "Updating Wakapi LXC"
+    $STD apk -U upgrade
+    msg_ok "Updated Wakapi LXC"
+
+    msg_info "Creating backup"
+    mkdir -p /opt/wakapi-backup
+    cp /opt/wakapi/config.yml /opt/wakapi/wakapi_db.db /opt/wakapi-backup/
+    msg_ok "Created backup"
+
+    CLEAN_INSTALL=1 fetch_and_deploy_gh_release "wakapi" "muety/wakapi" "tarball"
+
+    msg_info "Configuring Wakapi"
+    cd /opt/wakapi
+    $STD go mod download
+    $STD go build -o wakapi
+    cp /opt/wakapi-backup/config.yml /opt/wakapi/
+    cp /opt/wakapi-backup/wakapi_db.db /opt/wakapi/
+    rm -rf /opt/wakapi-backup
+    msg_ok "Configured Wakapi"
+
+    msg_info "Starting Service"
+    $STD rc-service wakapi start
+    msg_ok "Started Service"
+    msg_ok "Updated successfully"
+  else
+    msg_ok "No update required. ${APP} is already at ${RELEASE}"
+  fi
+  exit 0
+}
+
+start
+build_container
+description
+
+msg_ok "Completed successfully!\n"
+echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"
+echo -e "${INFO}${YW} Access it using the following URL:${CL}"
+echo -e "${TAB}${GATEWAY}${BGN}http://${IP}:3000${CL}"

ct/degoog.sh

@@ -1,73 +0,0 @@
-#!/usr/bin/env bash
-source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/misc/build.func)
-# Copyright (c) 2021-2026 community-scripts ORG
-# Author: vhsdream
-# License: MIT | https://github.com/community-scripts/ProxmoxVED/raw/main/LICENSE
-# Source: https://github.com/fccview/degoog
-
-APP="degoog"
-var_tags="${var_tags:-search;privacy;plugins}"
-var_cpu="${var_cpu:-2}"
-var_ram="${var_ram:-2048}"
-var_disk="${var_disk:-6}"
-var_os="${var_os:-debian}"
-var_version="${var_version:-13}"
-var_unprivileged="${var_unprivileged:-1}"
-
-header_info "$APP"
-variables
-color
-catch_errors
-
-function update_script() {
-  header_info
-  check_container_storage
-  check_container_resources
-
-  if [[ ! -d /opt/degoog ]]; then
-    msg_error "No ${APP} Installation Found!"
-    exit
-  fi
-
-  if check_for_gh_release "degoog" "fccview/degoog"; then
-    msg_info "Stopping Service"
-    systemctl stop degoog
-    msg_ok "Stopped Service"
-
-    msg_info "Backing up Configuration & Data"
-    [[ -f /opt/degoog/.env ]] && cp /opt/degoog/.env /opt/degoog.env.bak
-    [[ -d /opt/degoog/data ]] && mv /opt/degoog/data /opt/degoog_data_backup
-    msg_ok "Backed up Configuration & Data"
-
-    if ! command -v bun >/dev/null 2>&1; then
-      msg_info "Installing Bun"
-      export BUN_INSTALL="/root/.bun"
-      curl -fsSL https://bun.sh/install | $STD bash
-      ln -sf /root/.bun/bin/bun /usr/local/bin/bun
-      ln -sf /root/.bun/bin/bunx /usr/local/bin/bunx
-      msg_ok "Installed Bun"
-    fi
-
-    CLEAN_INSTALL=1 fetch_and_deploy_gh_release "degoog" "fccview/degoog" "prebuild" "latest" "/opt/degoog" "degoog_*_prebuild.tar.gz"
-
-    msg_info "Restoring Configuration & Data"
-    [[ -f /opt/degoog.env.bak ]] && mv /opt/degoog.env.bak /opt/degoog/.env
-    [[ -d /opt/degoog_data_backup ]] && mv /opt/degoog_data_backup /opt/degoog/data
-    msg_ok "Restored Configuration & Data"
-
-    msg_info "Starting Service"
-    systemctl start degoog
-    msg_ok "Started Service"
-    msg_ok "Updated successfully!"
-  fi
-  exit
-}
-
-start
-build_container
-description
-
-msg_ok "Completed Successfully!\n"
-echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"
-echo -e "${INFO}${YW} Access it using the following URL:${CL}"
-echo -e "${TAB}${GATEWAY}${BGN}http://${IP}:4444${CL}"

docs/contribution/CONTRIBUTING.md

@@ -1,142 +1,106 @@
+
 # Community Scripts Contribution Guide
 
-## Welcome to the community-scripts repository
+## **Welcome to the communty-scripts Repository!** 
 
-These documents outline the coding standards and contribution flow for the ProxmoxVED repository.
+📜 These documents outline the essential coding standards for all our scripts and JSON files. Adhering to these standards ensures that our codebase remains consistent, readable, and maintainable. By following these guidelines, we can improve collaboration, reduce errors, and enhance the overall quality of our project.
 
-The important reality check is simple:
+### Why Coding Standards Matter
 
-- contributors primarily submit shell scripts
-- website metadata is **not** contributed as repo JSON files
-- metadata changes belong to the website / maintainer workflow
+Coding standards are crucial for several reasons:
 
-## Scope of these documents
+1. **Consistency**: Consistent code is easier to read, understand, and maintain. It helps new team members quickly get up to speed and reduces the learning curve.
+2. **Readability**: Clear and well-structured code is easier to debug and extend. It allows developers to quickly identify and fix issues.
+3. **Maintainability**: Code that follows a standard structure is easier to refactor and update. It ensures that changes can be made with minimal risk of introducing new bugs.
+4. **Collaboration**: When everyone follows the same standards, it becomes easier to collaborate on code. It reduces friction and misunderstandings during code reviews and merges.
 
-This contribution guide covers:
+### Scope of These Documents
 
-- `ct/$AppName.sh` scripts for container creation and update entrypoints
-- `install/$AppName-install.sh` scripts for in-container installation logic
-- the supporting workflow for testing from your fork before opening a PR
+These documents cover the coding standards for the following types of files in our project:
 
-## Getting started
+- **`install/$AppName-install.sh` Scripts**: These scripts are responsible for the installation of applications.
+- **`ct/$AppName.sh` Scripts**: These scripts handle the creation and updating of containers.
+- **`json/$AppName.json`**: These files store structured data and are used for the website.
 
-Before contributing, set up:
+Each section provides detailed guidelines on various aspects of coding, including shebang usage, comments, variable naming, function naming, indentation, error handling, command substitution, quoting, script structure, and logging. Additionally, examples are provided to illustrate the application of these standards.
 
-1. Visual Studio Code or another editor with ShellCheck support
-2. a fork of `community-scripts/ProxmoxVED`
-3. a local clone of your fork
+By following the coding standards outlined in this document, we ensure that our scripts and JSON files are of high quality, making our project more robust and easier to manage. Please refer to this guide whenever you create or update scripts and JSON files to maintain a high standard of code quality across the project. 📚🔍
 
-### Recommended extensions
+Let's work together to keep our codebase clean, efficient, and maintainable! 💪🚀
 
-- [Shell Syntax](https://marketplace.visualstudio.com/items?itemName=bmalehorn.shell-syntax)
-- [ShellCheck](https://marketplace.visualstudio.com/items?itemName=timonwong.shellcheck)
-- [Shell Format](https://marketplace.visualstudio.com/items?itemName=foxundermoon.shell-format)
 
-### Templates
+## Getting Started
 
-Use these templates as your starting point:
+Before contributing, please ensure that you have the following setup:
 
-- [CT template: `AppName.sh`](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/ct/AppName.sh)
-- [Install template: `AppName-install.sh`](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/install/AppName-install.sh)
+1. **Visual Studio Code** (recommended for script development)
+2. **Recommended VS Code Extensions:**
+   - [Shell Syntax](https://marketplace.visualstudio.com/items?itemName=bmalehorn.shell-syntax)
+   - [ShellCheck](https://marketplace.visualstudio.com/items?itemName=timonwong.shellcheck)
+   - [Shell Format](https://marketplace.visualstudio.com/items?itemName=foxundermoon.shell-format)
 
-## Script types
+### Important Notes
+- Use [AppName.sh](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/ct/AppName.sh) and [AppName-install.sh](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/install/AppName-install.sh) as templates when creating new scripts.
 
-### Application script: `ct/AppName.sh`
+---
 
-Reference guide:
+# 🚀 The Application Script (ct/AppName.sh)
 
-- [CT coding guide for `AppName.sh`](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/ct/AppName.md)
+- You can find all coding standards, as well as the structure for this file [here](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/ct/AppName.md).
+- These scripts are responsible for container creation, setting the necessary variables and handling the update of the application once installed.
 
-This script is responsible for:
+---
 
-- host-side container orchestration
-- app variables and defaults
-- update wiring for the installed app
+# 🛠 The Installation Script (install/AppName-install.sh)
 
-### Installation script: `install/AppName-install.sh`
+- You can find all coding standards, as well as the structure for this file [here](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/install/AppName-install.md).
+- These scripts are responsible for the installation of the application.
 
-Reference guide:
+---
 
-- [Install coding guide for `AppName-install.sh`](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/install/AppName-install.md)
+## 🚀 Building Your Own Scripts
 
-This script is responsible for:
+Start with the [template script](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/install/AppName-install.sh)
 
-- container-internal installation logic
-- package/runtime setup
-- final application configuration
+---
 
-## Contribution process
+## 🤝 Contribution Process
 
 ### 1. Fork the repository
+Fork to your GitHub account
 
-Fork `community-scripts/ProxmoxVED` to your GitHub account.
-
-### 2. Clone your fork
-
+### 2. Clone your fork on your local environment 
 ```bash
 git clone https://github.com/yourUserName/ForkName
 ```
 
-### 3. Create a branch
-
+### 3. Create a new branch
 ```bash
 git switch -c your-feature-branch
 ```
 
-### 4. Configure your fork for testing
-
-Use the helper script:
-
-```bash
-bash docs/contribution/setup-fork.sh --full
-```
-
-This prepares the raw GitHub URLs in your working copy so you can test against your own fork instead of the upstream repository.
-
-### 5. Build and test from your fork
-
-Use the curl/bash execution model that matches real user behavior, for example:
-
-```bash
-bash -c "$(curl -fsSL https://raw.githubusercontent.com/<USER>/<REPO>/refs/heads/<BRANCH>/ct/myapp.sh)"
-```
-
-Do **not** document or optimize only for local manual execution if the real path is curl-based execution.
-
-### 6. Commit only your intended contribution
+### 4. Change paths in build.func install.func and AppName.sh
+To be able to develop from your own branch you need to change `https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main` to `https://raw.githubusercontent.com/[USER]/[REPOSITORY]/refs/heads/[BRANCH]`. You need to make this change atleast in misc/build.func misc/install.func and in your ct/AppName.sh. This change is only for testing. Before opening a Pull Request you should change this line change all this back to point to `https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main`.
 
+### 4. Commit changes (without build.func and install.func!)
 ```bash
 git commit -m "Your commit message"
 ```
 
-### 7. Push your branch
-
+### 5. Push to your fork
 ```bash
 git push origin your-feature-branch
 ```
 
-### 8. Open a pull request
+### 6. Create a Pull Request
+Open a Pull Request from your feature branch to the main repository branch. You must only include your **$AppName.sh**, **$AppName-install.sh** and **$AppName.json** files in the pull request.
 
-Open a PR from your branch to `community-scripts/ProxmoxVED/main`.
+---
 
-Your PR should contain only the files that belong to the script contribution itself, typically:
-
-- `ct/myapp.sh`
-- `install/myapp-install.sh`
-
-## Website metadata
-
-Website metadata is maintained outside this repository's script contribution flow.
-
-That means:
-
-- do not add repo JSON metadata files as part of the normal contribution path
-- do not assume a `frontend/public/json/...` workflow exists for the live site
-- route metadata creation or metadata changes through the website / maintainer workflow
-
-## Pages
+## 📚 Pages
 
 - [CT Template: AppName.sh](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/ct/AppName.sh)
 - [Install Template: AppName-install.sh](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/install/AppName-install.sh)
-- [Fork setup guide](./FORK_SETUP.md)
-- [Contribution README](./README.md)
+- [JSON Template: AppName.json](https://github.com/community-scripts/ProxmoxVED/blob/main/.github/CONTRIBUTOR_AND_GUIDES/json/AppName.json)
+
+

docs/misc/README.md

@@ -1,25 +1,15 @@
 # Misc Documentation
 
-This directory documents the shared Bash function libraries under `misc/`.
-
-The important implementation detail is that these libraries are **not independent islands**:
-
-- `build.func` orchestrates host-side CT creation.
-- `api.func` is the canonical source of telemetry and exit-code explanations.
-- `error_handler.func` wraps trap handling and falls back to `explain_exit_code()` if `api.func` was not loaded yet.
-- `install.func` runs inside the container and bootstraps `core.func` + `error_handler.func` first, then downloads `tools.func` after the OS update stage.
-- `tools.func` is the large Debian/Ubuntu helper toolbox for repository management, retries, releases, services, language runtimes, databases, GPU helpers, and update workflows.
+This directory contains comprehensive documentation for all function libraries and components of the Proxmox Community Scripts project. Each section is organized as a dedicated subdirectory with detailed references, examples, and integration guides.
 
 ---
 
 ## 🏗️ **Core Function Libraries**
 
 ### 📁 [build.func/](./build.func/)
-
 **Core LXC Container Orchestration** - Main orchestrator for Proxmox LXC container creation
 
 **Contents:**
-
 - BUILD_FUNC_FLOWCHART.md - Visual execution flows and decision trees
 - BUILD_FUNC_ARCHITECTURE.md - System architecture and design
 - BUILD_FUNC_ENVIRONMENT_VARIABLES.md - Complete environment variable reference
@@ -33,11 +23,9 @@ The important implementation detail is that these libraries are **not independen
 ---
 
 ### 📁 [core.func/](./core.func/)
-
-**System Utilities & Foundation** - Shared runtime foundation for logging, prompts, validation, and execution control
+**System Utilities & Foundation** - Essential utility functions and system checks
 
 **Contents:**
-
 - CORE_FLOWCHART.md - Visual execution flows
 - CORE_FUNCTIONS_REFERENCE.md - Complete function reference
 - CORE_INTEGRATION.md - Integration points
@@ -49,11 +37,9 @@ The important implementation detail is that these libraries are **not independen
 ---
 
 ### 📁 [error_handler.func/](./error_handler.func/)
-
-**Error Handling & Signal Management** - Trap orchestration, cleanup, and abort telemetry
+**Error Handling & Signal Management** - Comprehensive error handling and signal trapping
 
 **Contents:**
-
 - ERROR_HANDLER_FLOWCHART.md - Visual error handling flows
 - ERROR_HANDLER_FUNCTIONS_REFERENCE.md - Function reference
 - ERROR_HANDLER_INTEGRATION.md - Integration with other components
@@ -65,45 +51,39 @@ The important implementation detail is that these libraries are **not independen
 ---
 
 ### 📁 [api.func/](./api.func/)
-
-**Telemetry & Diagnostics Runtime** - Anonymous telemetry reporting, progress tracking, and canonical exit-code mapping
+**Proxmox API Integration** - API communication and diagnostic reporting
 
 **Contents:**
-
 - API_FLOWCHART.md - API communication flows
 - API_FUNCTIONS_REFERENCE.md - Function reference
 - API_INTEGRATION.md - Integration points
 - API_USAGE_EXAMPLES.md - Practical examples
 - README.md - Overview and quick reference
 
-**Key Functions**: `post_to_api()`, `post_to_api_vm()`, `post_progress_to_api()`, `post_update_to_api()`, `explain_exit_code()`
+**Key Functions**: `post_to_api()`, `post_update_to_api()`, `get_error_description()`
 
 ---
 
 ## 📦 **Installation & Setup Function Libraries**
 
 ### 📁 [install.func/](./install.func/)
-
-**Container Installation Workflow** - Container bootstrap inside the LXC
+**Container Installation Workflow** - Installation orchestration for container-internal setup
 
 **Contents:**
-
 - INSTALL_FUNC_FLOWCHART.md - Installation workflow diagrams
 - INSTALL_FUNC_FUNCTIONS_REFERENCE.md - Complete function reference
 - INSTALL_FUNC_INTEGRATION.md - Integration with build and tools
 - INSTALL_FUNC_USAGE_EXAMPLES.md - Practical examples
 - README.md - Overview and quick reference
 
-**Key Functions**: `setting_up_container()`, `network_check()`, `update_os()`, `motd_ssh()`, `customize()`
+**Key Functions**: `setting_up_container()`, `network_check()`, `update_os()`, `motd_ssh()`, `cleanup_lxc()`
 
 ---
 
 ### 📁 [tools.func/](./tools.func/)
-
-**Package & Tool Installation** - Repository, package, release, runtime, and service toolbox
+**Package & Tool Installation** - Robust package management and 30+ tool installation functions
 
 **Contents:**
-
 - TOOLS_FUNC_FLOWCHART.md - Package management flows
 - TOOLS_FUNC_FUNCTIONS_REFERENCE.md - 30+ function reference
 - TOOLS_FUNC_INTEGRATION.md - Integration with install workflows
@@ -111,16 +91,14 @@ The important implementation detail is that these libraries are **not independen
 - TOOLS_FUNC_ENVIRONMENT_VARIABLES.md - Configuration reference
 - README.md - Overview and quick reference
 
-**Key Functions**: `curl_with_retry()`, `setup_deb822_repo()`, `install_packages_with_retry()`, `setup_mariadb()`, `setup_postgresql()`, `get_latest_github_release()`
+**Key Functions**: `setup_nodejs()`, `setup_php()`, `setup_mariadb()`, `setup_docker()`, `setup_deb822_repo()`, `pkg_install()`, `pkg_update()`
 
 ---
 
 ### 📁 [alpine-install.func/](./alpine-install.func/)
-
 **Alpine Container Setup** - Alpine Linux-specific installation functions
 
 **Contents:**
-
 - ALPINE_INSTALL_FUNC_FLOWCHART.md - Alpine setup flows
 - ALPINE_INSTALL_FUNC_FUNCTIONS_REFERENCE.md - Function reference
 - ALPINE_INSTALL_FUNC_INTEGRATION.md - Integration points
@@ -132,11 +110,9 @@ The important implementation detail is that these libraries are **not independen
 ---
 
 ### 📁 [alpine-tools.func/](./alpine-tools.func/)
-
 **Alpine Tool Installation** - Alpine-specific package and tool installation
 
 **Contents:**
-
 - ALPINE_TOOLS_FUNC_FLOWCHART.md - Alpine package flows
 - ALPINE_TOOLS_FUNC_FUNCTIONS_REFERENCE.md - Function reference
 - ALPINE_TOOLS_FUNC_INTEGRATION.md - Integration with Alpine workflows
@@ -148,11 +124,9 @@ The important implementation detail is that these libraries are **not independen
 ---
 
 ### 📁 [cloud-init.func/](./cloud-init.func/)
-
 **VM Cloud-Init Configuration** - Cloud-init and VM provisioning functions
 
 **Contents:**
-
 - CLOUD_INIT_FUNC_FLOWCHART.md - Cloud-init flows
 - CLOUD_INIT_FUNC_FUNCTIONS_REFERENCE.md - Function reference
 - CLOUD_INIT_FUNC_INTEGRATION.md - Integration points
@@ -171,24 +145,18 @@ The important implementation detail is that these libraries are **not independen
 ├─────────────────────────────────────────────┤
 │                                             │
 │  ct/AppName.sh                              │
-│      ↓ sources                              │
+│      ↓ (sources)                            │
 │  build.func                                 │
-│      ├─ sources api.func                    │
-│      ├─ sources core.func                   │
-│      ├─ sources error_handler.func          │
-│      ├─ loads variables/settings/prompts    │
-│      └─ creates container + launch phase    │
-│      ↓ pct exec / lxc-attach                │
+│      ├─ variables()                         │
+│      ├─ build_container()                   │
+│      └─ advanced_settings()                 │
+│      ↓ (calls pct create with)              │
 │  install/appname-install.sh                 │
-│      ↓ sources install.func                 │
-│      ├─ sources core.func                   │
-│      ├─ sources error_handler.func          │
-│      ├─ load_functions()                    │
-│      ├─ catch_errors()                      │
-│      ├─ network_check()                     │
-│      ├─ update_os()                         │
-│      │   └─ downloads + sources tools.func  │
-│      └─ app install uses tools.func         │
+│      ↓ (sources)                            │
+│      ├─ core.func      (colors, messaging)  │
+│      ├─ error_handler.func (error trapping) │
+│      ├─ install.func   (setup/network)      │
+│      └─ tools.func     (packages/tools)     │
 │                                             │
 └─────────────────────────────────────────────┘
 
@@ -223,17 +191,17 @@ The important implementation detail is that these libraries are **not independen
 
 ## 📊 **Documentation Quick Stats**
 
-| Library             | Files | Functions |   Status    |
-| ------------------- | :---: | :-------: | :---------: |
-| build.func          |   7   |    50+    | ✅ Complete |
-| core.func           |   5   |    20+    | ✅ Complete |
-| error_handler.func  |   5   |    10+    | ✅ Complete |
-| api.func            |   5   |    5+     | ✅ Complete |
-| install.func        |   5   |    8+     | ✅ Complete |
-| tools.func          |   6   |    30+    | ✅ Complete |
-| alpine-install.func |   5   |    6+     | ✅ Complete |
-| alpine-tools.func   |   5   |    15+    | ✅ Complete |
-| cloud-init.func     |   5   |    12+    | ✅ Complete |
+| Library | Files | Functions | Status |
+|---------|:---:|:---:|:---:|
+| build.func | 7 | 50+ | ✅ Complete |
+| core.func | 5 | 20+ | ✅ Complete |
+| error_handler.func | 5 | 10+ | ✅ Complete |
+| api.func | 5 | 5+ | ✅ Complete |
+| install.func | 5 | 8+ | ✅ Complete |
+| tools.func | 6 | 30+ | ✅ Complete |
+| alpine-install.func | 5 | 6+ | ✅ Complete |
+| alpine-tools.func | 5 | 15+ | ✅ Complete |
+| cloud-init.func | 5 | 12+ | ✅ Complete |
 
 **Total**: 9 function libraries, 48 documentation files, 150+ functions
 
@@ -242,20 +210,16 @@ The important implementation detail is that these libraries are **not independen
 ## 🚀 **Getting Started**
 
 ### For Container Creation Scripts
-
-Start with: **[build.func/](./build.func/)** → **[core.func/](./core.func/)** → **[error_handler.func/](./error_handler.func/)** → **[api.func/](./api.func/)** → **[install.func/](./install.func/)** → **[tools.func/](./tools.func/)**
+Start with: **[build.func/](./build.func/)** → **[tools.func/](./tools.func/)** → **[install.func/](./install.func/)**
 
 ### For Alpine Containers
-
 Start with: **[alpine-install.func/](./alpine-install.func/)** → **[alpine-tools.func/](./alpine-tools.func/)**
 
 ### For VM Provisioning
-
 Start with: **[cloud-init.func/](./cloud-init.func/)**
 
 ### For Troubleshooting
-
-Start with: **[error_handler.func/](./error_handler.func/)** → **[api.func/](./api.func/)**
+Start with: **[error_handler.func/](./error_handler.func/)** → **[EXIT_CODES.md](../EXIT_CODES.md)**
 
 ---
 
@@ -287,7 +251,6 @@ function-library/
 ```
 
 **Advantages**:
-
 - ✅ Consistent navigation across all libraries
 - ✅ Quick reference sections in each README
 - ✅ Visual flowcharts for understanding
@@ -310,12 +273,11 @@ All documentation follows these standards:
 
 ---
 
-## ✅ **Last Updated**: Based on live `misc/*` code verification
-
+## ✅ **Last Updated**: December 2025
 **Maintainers**: community-scripts team
 **License**: MIT
-**Status**: Canonical overviews aligned to live code; deeper generated subpages may still require occasional drift cleanup
+**Status**: All 9 libraries fully documented and standardized
 
 ---
 
-_When documentation conflicts with the live shell implementation, prefer the files under `ProxmoxVE` / `ProxmoxVED` `misc/`._
+*This directory contains specialized documentation for specific components of the Proxmox Community Scripts project.*

install/alpine-wakapi-install.sh

@@ -0,0 +1,61 @@
+#!/usr/bin/env bash
+
+# Copyright (c) 2021-2026 community-scripts ORG
+# Author: Slaviša Arežina (tremor021)
+# License: MIT | https://github.com/community-scripts/ProxmoxVED/raw/main/LICENSE
+# Source: https://wakapi.dev/ | https://github.com/muety/wakapi
+
+source /dev/stdin <<<"$FUNCTIONS_FILE_PATH"
+color
+verb_ip6
+catch_errors
+setting_up_container
+network_check
+update_os
+
+msg_info "Installing Dependencies"
+$STD apk add --no-cache \
+  ca-certificates \
+  tzdata
+$STD update-ca-certificates
+$STD apk add --no-cache go --repository=https://dl-cdn.alpinelinux.org/alpine/edge/community
+msg_ok "Installed Dependencies"
+
+fetch_and_deploy_gh_release "wakapi" "muety/wakapi" "tarball"
+
+msg_info "Configuring Wakapi"
+LOCAL_IP=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1)
+cd /opt/wakapi
+$STD go mod download
+$STD go build -o wakapi
+cp config.default.yml config.yml
+sed -i 's/listen_ipv6: ::1/listen_ipv6: "-"/g' config.yml
+sed -i 's/listen_ipv4: 127.0.0.1/listen_ipv4: "0.0.0.0"/g' config.yml
+sed -i "s/public_url: http:\/\/localhost:3000/public_url: http:\/\/$LOCAL_IP:3000/g" config.yml
+msg_ok "Configured Wakapi"
+
+msg_info "Enabling Wakapi Service"
+cat <<EOF >/etc/init.d/wakapi
+#!/sbin/openrc-run
+description="Wakapi Service"
+directory="/opt/wakapi"
+command="/opt/wakapi/wakapi"
+command_args="-config config.yml"
+command_background="true"
+command_user="root"
+pidfile="/var/run/wakapi.pid"
+
+depend() {
+    use net
+}
+EOF
+chmod +x /etc/init.d/wakapi
+$STD rc-update add wakapi default
+msg_ok "Enabled Wakapi Service"
+
+msg_info "Starting Wakapi"
+$STD rc-service wakapi start
+msg_ok "Started Wakapi"
+
+motd_ssh
+customize

install/degoog-install.sh

@@ -1,88 +0,0 @@
-#!/usr/bin/env bash
-
-# Copyright (c) 2021-2026 community-scripts ORG
-# Author: vhsdream
-# License: MIT | https://github.com/community-scripts/ProxmoxVED/raw/main/LICENSE
-# Source: https://github.com/fccview/degoog
-
-source /dev/stdin <<<"$FUNCTIONS_FILE_PATH"
-color
-verb_ip6
-catch_errors
-setting_up_container
-network_check
-update_os
-
-msg_info "Installing Dependencies"
-$STD apt install -y \
-  git \
-  unzip
-msg_ok "Installed Dependencies"
-
-msg_info "Installing Bun"
-export BUN_INSTALL="/root/.bun"
-curl -fsSL https://bun.sh/install | $STD bash
-ln -sf /root/.bun/bin/bun /usr/local/bin/bun
-ln -sf /root/.bun/bin/bunx /usr/local/bin/bunx
-msg_ok "Installed Bun"
-
-fetch_and_deploy_gh_release "degoog" "fccview/degoog" "prebuild" "latest" "/opt/degoog" "degoog_*_prebuild.tar.gz"
-
-msg_info "Setting up degoog"
-mkdir -p /opt/degoog/data/{engines,plugins,themes,store}
-
-cat <<EOF >/opt/degoog/.env
-DEGOOG_PORT=4444
-DEGOOG_ENGINES_DIR=/opt/degoog/data/engines
-DEGOOG_PLUGINS_DIR=/opt/degoog/data/plugins
-DEGOOG_THEMES_DIR=/opt/degoog/data/themes
-DEGOOG_ALIASES_FILE=/opt/degoog/data/aliases.json
-DEGOOG_PLUGIN_SETTINGS_FILE=/opt/degoog/data/plugin-settings.json
-# DEGOOG_SETTINGS_PASSWORDS=changeme
-# DEGOOG_PUBLIC_INSTANCE=false
-# LOGGER=debug
-EOF
-
-if [[ ! -f /opt/degoog/data/aliases.json ]]; then
-  cat <<EOF >/opt/degoog/data/aliases.json
-{}
-EOF
-fi
-
-if [[ ! -f /opt/degoog/data/plugin-settings.json ]]; then
-  cat <<EOF >/opt/degoog/data/plugin-settings.json
-{}
-EOF
-fi
-
-if [[ ! -f /opt/degoog/data/repos.json ]]; then
-  cat <<EOF >/opt/degoog/data/repos.json
-[]
-EOF
-fi
-msg_ok "Set up degoog"
-
-msg_info "Creating Service"
-cat <<EOF >/etc/systemd/system/degoog.service
-[Unit]
-Description=degoog
-After=network.target
-
-[Service]
-Type=simple
-User=root
-WorkingDirectory=/opt/degoog
-EnvironmentFile=/opt/degoog/.env
-ExecStart=/usr/local/bin/bun run src/server/index.ts
-Restart=on-failure
-RestartSec=5
-
-[Install]
-WantedBy=multi-user.target
-EOF
-systemctl enable -q --now degoog
-msg_ok "Created Service"
-
-motd_ssh
-customize
-cleanup_lxc

json/alpine-wakapi.json

@@ -0,0 +1,40 @@
+{
+  "name": "Alpine-Wakapi",
+  "slug": "alpine-wakapi",
+  "categories": [
+    9
+  ],
+  "date_created": "2026-02-16",
+  "type": "ct",
+  "updateable": true,
+  "privileged": false,
+  "interface_port": 3000,
+  "documentation": "https://github.com/muety/wakapi/wiki",
+  "website": "https://wakapi.dev/",
+  "logo": "https://cdn.jsdelivr.net/gh/selfhst/icons@main/webp/wakapi.webp",
+  "config_path": "/opt/wakapi/config.yml",
+  "description": "Wakapi is an open-source tool that helps you keep track of the time you have spent coding on different projects in different programming languages and more. Ideal for statistics freaks and anyone else.",
+  "install_methods": [
+    {
+      "type": "default",
+      "script": "ct/alpine-wakapi.sh",
+      "resources": {
+        "cpu": 1,
+        "ram": 512,
+        "hdd": 4,
+        "os": "alpine",
+        "version": "3.23"
+      }
+    }
+  ],
+  "default_credentials": {
+    "username": null,
+    "password": null
+  },
+  "notes": [
+    {
+      "text": "The first user created will be an admin.",
+      "type": "warning"
+    }
+  ]
+}

json/degoog.json

@@ -1,44 +0,0 @@
-{
-    "name": "degoog",
-    "slug": "degoog",
-    "categories": [
-        0
-    ],
-    "date_created": "2026-03-20",
-    "type": "ct",
-    "updateable": true,
-    "privileged": false,
-    "interface_port": 4444,
-    "documentation": "https://fccview.github.io/degoog/",
-    "website": "https://github.com/fccview/degoog",
-    "logo": "https://raw.githubusercontent.com/fccview/degoog/main/src/public/images/degoog-logo.png",
-    "config_path": "/opt/degoog/.env",
-    "description": "Search aggregator that queries multiple engines and supports plugins, themes, and extension repositories.",
-    "install_methods": [
-        {
-            "type": "default",
-            "script": "ct/degoog.sh",
-            "resources": {
-                "cpu": 2,
-                "ram": 2048,
-                "hdd": 6,
-                "os": "Debian",
-                "version": "13"
-            }
-        }
-    ],
-    "default_credentials": {
-        "username": null,
-        "password": null
-    },
-    "notes": [
-        {
-            "text": "Project is currently marked beta upstream and not intended for production use yet.",
-            "type": "warning"
-        },
-        {
-            "text": "Add extension store repositories in Settings after first start (official repo: https://github.com/fccview/fccview-degoog-extensions).",
-            "type": "info"
-        }
-    ]
-}