Update script count from 600 to 700 in README

Say how an update is actually run, and show the fork case first
The update block told people to reach the container with pct, which is not how anyone gets there; the website says to type "update" in the container console, so say that. VM scripts have no updater at all, which the page did not mention. The fork example exported the core URL, which only matters when the engine itself is being changed -- the ordinary case is a fork of the scripts, and it needs COMMUNITY_SCRIPTS_URL or the engine looks for the install half upstream. Neither needs exporting.
2026-10-26 23:45:13 +01:00 · 2026-10-26 10:44:19 +01:00 · 2026-10-26 10:41:19 +01:00 · 2026-10-26 10:37:33 +01:00 · 2026-10-26 10:35:06 +01:00 · 2026-10-26 10:27:13 +01:00
15 changed files with 161 additions and 117 deletions
@@ -583,18 +583,12 @@ Exercise vigilance regarding copycat or coat-tailing sites that seek to exploit

  - #### 🐞 Bug Fixes

-    - Fix service name case for Splunkd [@CerberusStyle](https://github.com/CerberusStyle) ([#18238](https://github.com/community-scripts/ProxmoxVE/pull/18238))
-    - VMs: pass the machine type, CPU, disk cache and discard settings to qm [@MickLesk](https://github.com/MickLesk) ([#18232](https://github.com/community-scripts/ProxmoxVE/pull/18232))
    - excalidash: bump Node.js from 20 to 24 [@github-actions[bot]](https://github.com/github-actions[bot]) ([#18213](https://github.com/community-scripts/ProxmoxVE/pull/18213))
    - readmeabook: bump Node.js from 20 to 24 [@github-actions[bot]](https://github.com/github-actions[bot]) ([#18217](https://github.com/community-scripts/ProxmoxVE/pull/18217))
    - homepage: bump Node.js from 22 to 24 [@github-actions[bot]](https://github.com/github-actions[bot]) ([#18214](https://github.com/community-scripts/ProxmoxVE/pull/18214))
    - remove old -install.sh (verdaccio) [@github-actions[bot]](https://github.com/github-actions[bot]) ([#18218](https://github.com/community-scripts/ProxmoxVE/pull/18218))
    - meshcentral: bump Node.js from 22 to 24 [@github-actions[bot]](https://github.com/github-actions[bot]) ([#18215](https://github.com/community-scripts/ProxmoxVE/pull/18215))

-### 💾 Core
-
-  - feat: create containers from the linuxcontainers.org catalog when Proxmox has no template [@MickLesk](https://github.com/MickLesk) ([core#25](https://github.com/community-scripts/core/pull/25))
-
 ## 2026-10-25

 ### 🆕 New Scripts
@@ -191,7 +191,6 @@ create` still ran and the container was still built.
 ## Notes

 - **Website metadata** (name, description, logo, tags) is managed via the website — use the "Report Issue" link on any script page to request changes. Do not submit metadata changes via repo files.
- **JSON files** in `json/` define script properties used by the website. See existing files for structure reference.
 - Keep PRs small and focused. One fix or feature per PR is ideal.
 - PRs with **new scripts** opened against ProxmoxVE will be closed — submit them to [DevScripts](https://github.com/community-scripts/DevScripts) instead.
 - PRs that fail CI checks will not be merged.
@@ -1,16 +1,17 @@
 <div align="center">
-  <img src="https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/images/logo-81x112.png" height="112px" alt="Proxmox VE Helper-Scripts Logo" />
+  <a href="misc/images/community-scripts.svg"><img src="misc/images/community-scripts.png" width="112" height="112" alt="Community Scripts — Proxmox VE logo" /></a>
+  <!-- Editable artwork: misc/images/community-scripts.svg; PNG export: 512 × 512. -->

-  <h1>Proxmox VE Helper-Scripts</h1>
-  <p><strong>One-command installations for services, containers, and VMs on Proxmox VE</strong><br/>
+  <h1>Community Scripts — Proxmox VE</h1>
+  <p><strong>One-command installations for services, containers and VMs on Proxmox VE</strong><br/>
  A community project — built on the foundation of <a href="https://github.com/tteck">@tteck</a>'s original work</p>

  <p>
-    <a href="https://community-scripts.org"><img src="https://img.shields.io/badge/Website-community--scripts.org-4c9b3f?style=flat-square" /></a>
-    <a href="https://discord.gg/3AnUqsXnmK"><img src="https://img.shields.io/badge/Discord-Join_us-7289da?style=flat-square&logo=discord&logoColor=white" /></a>
-    <a href="https://github.com/community-scripts/ProxmoxVE/stargazers"><img src="https://img.shields.io/github/stars/community-scripts/ProxmoxVE?style=flat-square&label=Stars&color=f5a623" /></a>
-    <a href="https://github.com/community-scripts/ProxmoxVE/blob/main/CHANGELOG.md"><img src="https://img.shields.io/badge/Changelog-view-6c5ce7?style=flat-square" /></a>
-    <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue?style=flat-square" /></a>
+    <a href="https://community-scripts.org"><img src="https://img.shields.io/badge/Website-community--scripts.org-4c9b3f?style=flat-square" alt="Website" /></a>
+    <a href="https://discord.gg/3AnUqsXnmK"><img src="https://img.shields.io/badge/Discord-Join_us-7289da?style=flat-square&logo=discord&logoColor=white" alt="Discord" /></a>
+    <a href="https://github.com/community-scripts/ProxmoxVE/stargazers"><img src="https://img.shields.io/github/stars/community-scripts/ProxmoxVE?style=flat-square&label=Stars&color=f5a623" alt="Stars" /></a>
+    <a href="https://github.com/community-scripts/ProxmoxVE/blob/main/CHANGELOG.md"><img src="https://img.shields.io/badge/Changelog-view-6c5ce7?style=flat-square" alt="Changelog" /></a>
+    <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue?style=flat-square" alt="License" /></a>
  </p>
 </div>

@@ -18,94 +19,147 @@

 ## What is this?

-**Simplify your Proxmox VE setup with community-driven automation scripts.**
+**The canonical application scripts.** More than 700 of them, covering home
+automation, media, networking, databases, monitoring, security and developer
+tooling. Paste one command into your Proxmox shell and the container or VM is
+built, configured and running.

-Install and configure popular self-hosted services with a single command — no manual package hunting, no config file archaeology. Paste a command into your Proxmox shell, answer a few prompts, and your container or VM is up and running.
+A script only describes *what* to install. Creating the container, asking the
+questions and handling the errors is the job of the shared engine in
+[core](https://github.com/community-scripts/core), which every script loads at
+start-up. The same scripts run unchanged on an Incus host through
+[the Incus repository](https://github.com/community-scripts/Incus).

-The collection covers hundreds of services across categories like home automation, media servers, networking tools, databases, monitoring stacks, and more.
+Ready-made commands for every application are on
+[community-scripts.org](https://community-scripts.org).
+
+---
+
+## Getting started
+
+1. Go to **[community-scripts.org](https://community-scripts.org)**
+2. Search for the service you want — Home Assistant, Nginx Proxy Manager, Jellyfin
+3. Copy the one-line install command from the script page
+4. Open your **Proxmox shell** and paste it
+5. Choose **Default** or **Advanced** and follow the prompts
+
+Each script page lists what the container includes, the default resources and
+the post-install notes.
+
+> These commands run as root on your host. Every script is readable in this
+> repository, and each script page links to its source — read it before you
+> paste it, as you would with any installer.
+
+---
+
+## How scripts work
+
+**Default** picks sensible resources and asks only what it has to. Most installs
+finish in a few minutes.
+
+**Advanced** hands you container settings, networking, storage backend and
+application options before anything is created.
+
+Every container gets an `update` command. Type it in the container console:
+
+```bash
+update
+```
+
+It updates the installed application and reaches settings that would otherwise
+mean editing config files by hand. VM scripts have no built-in updater — use the
+guest's own package manager.

 ---

 ## Requirements

-| Component      | Details                                          |
-| -------------- | ------------------------------------------------ |
-| **Proxmox VE** | Version 8.4, 9.0, 9.1, or 9.2                    |
-| **Host OS**    | Proxmox VE (Debian-based)                        |
-| **Access**     | Root shell access on the Proxmox host            |
-| **Network**    | Internet connection required during installation |
+| Component | Details |
+| --------- | ------- |
+| **Proxmox VE** | 8.0 – 8.4, or 9.0 – 9.2 |
+| **Access** | Root shell on the Proxmox host |
+| **Network** | Internet access during installation |
+
+Virtual machine scripts need the same versions as containers.

 ---

-## Getting Started
+## Repository map

-The fastest way to find and run scripts:
-
-1. Go to **[community-scripts.org](https://community-scripts.org)**
-2. Search for the service you want (e.g. "Home Assistant", "Nginx Proxy Manager", "Jellyfin")
-3. Copy the one-line install command from the script page
-4. Open your **Proxmox Shell** and paste it
-5. Choose between **Default** or **Advanced** setup and follow the prompts
-
-Each script page documents what the container includes, default resource allocation, and post-install notes.
+| Repository | Contains |
+| ---------- | -------- |
+| [core](https://github.com/community-scripts/core) | The engine — container and VM creation, the wizard, error handling |
+| **ProxmoxVE** (this repo) | Canonical application scripts, plus `tools/pve/`, `vm/` and `turnkey/` |
+| [Incus](https://github.com/community-scripts/Incus) | The same scripts on an Incus host, plus Incus VMs and host tooling |
+| [DevScripts](https://github.com/community-scripts/DevScripts) | Where new scripts are tested before they land here |

 ---

-## How Scripts Work
+## Layout

-Every script follows the same pattern:
+| Folder | Contents |
+| ------ | -------- |
+| `ct/` | Application scripts — the command you paste |
+| `install/` | What each script installs inside the container |
+| `vm/` | Virtual machine scripts |
+| `tools/pve/` | Host tooling: post-install, hardware passthrough, maintenance |
+| `turnkey/` | TurnKey Linux appliance helper |
+| `misc/` | Legacy engine copies — current scripts load [core](https://github.com/community-scripts/core) at runtime, so changes here never reach a running install |

-**Default mode** — Picks sensible resource defaults (CPU, RAM, storage) and asks only the minimum required questions. Most installs finish in under five minutes.
-
-**Advanced mode** — Gives you full control over container settings, networking, storage backends, and application-level configuration before anything is installed.
-
-After installation, each container ships with a **post-install helper** accessible from the Proxmox shell. It handles common tasks like:
-
- Applying updates to the installed service
- Changing application settings without manually editing config files
- Basic troubleshooting and log access
+Application metadata — name, description, logo, tags — is managed on the website,
+not in this repository. Use the **Report Issue** link on any script page to
+request a change.

 ---

-## What's Included
+## Testing a fork or branch

-The repository covers a wide range of categories. A few examples:
+Engine and scripts resolve independently, so either can point somewhere else.
+Put the variable on the command itself — nothing needs exporting.

-| Category        | Examples                                            |
-| --------------- | --------------------------------------------------- |
-| Home Automation | Home Assistant, Zigbee2MQTT, ESPHome, Node-RED      |
-| Media           | Jellyfin, Plex, Radarr, Sonarr, Immich              |
-| Networking      | AdGuard Home, Nginx Proxy Manager, Pi-hole, Traefik |
-| Monitoring      | Grafana, Prometheus, Uptime Kuma, Netdata           |
-| Databases       | PostgreSQL, MariaDB, Redis, InfluxDB                |
-| Security        | Vaultwarden, CrowdSec, Authentik                    |
-| Dev & Tools     | Gitea, Portainer, VS Code Server, n8n               |
+To run your own copy of the scripts:

-> Browse the full list at **[community-scripts.org/categories](https://community-scripts.org/categories)** — new scripts are added regularly.
+```bash
+COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/YOU/ProxmoxVE/my-branch \
+  bash -c "$(curl -fsSL https://raw.githubusercontent.com/YOU/ProxmoxVE/my-branch/ct/debian.sh)"
+```
+
+A `ct/` script fetched with `curl` cannot tell the engine where it came from, so
+without that variable it would look for its `install/` half upstream.
+
+Only when you are changing the engine itself:
+
+```bash
+COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/YOU/core/my-branch \
+  bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"
+```
+
+A local checkout of core wins over both — point at it with
+`COMMUNITY_SCRIPTS_CORE_DIR`.

 ---

 ## Contributing

-This project runs on community contributions. Whether you want to write new scripts, improve existing ones, or just report a bug — every bit helps.
+This project runs on community contributions. New scripts, fixes, bug reports —
+all of it helps.

-### Where to start
-
-| I want to…                            | Go here                                                                                           |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------- |
-| Add a **new** script                  | [DevScripts](https://github.com/community-scripts/DevScripts) — new scripts are tested here first |
-| Fix or improve an **existing** script | [Contributing Guidelines](CONTRIBUTING.md) — open a PR in this repo                               |
-| Report a bug or broken script         | [Issues](https://github.com/community-scripts/ProxmoxVE/issues)                                   |
-| Request a new script or feature       | [Discussions](https://github.com/community-scripts/ProxmoxVE/discussions)                         |
-| Report a security vulnerability       | [Security Policy](SECURITY.md)                                                                    |
-| Get help or chat with other users     | [Discord](https://discord.gg/3AnUqsXnmK)                                                          |
+| I want to… | Go here |
+| ---------- | ------- |
+| Add a **new** script | [DevScripts](https://github.com/community-scripts/DevScripts) — new scripts are tested there first |
+| Fix or improve an **existing** script | [Contributing Guidelines](CONTRIBUTING.md) — open a PR here |
+| Change how containers are built | [core](https://github.com/community-scripts/core) |
+| Report a bug or a broken script | [Issues](https://github.com/community-scripts/ProxmoxVE/issues) |
+| Request a script or a feature | [Discussions](https://github.com/community-scripts/ProxmoxVE/discussions) |
+| Report a security vulnerability | [Security Policy](SECURITY.md) |
+| Ask a question | [Discord](https://discord.gg/3AnUqsXnmK) |

 ### Before you open a PR

- **New scripts go to [DevScripts](https://github.com/community-scripts/DevScripts), not here.** PRs with new scripts opened directly against this repo will be closed.
- Bug fixes and improvements to existing scripts belong in this repo — read the [Contributing Guidelines](CONTRIBUTING.md) first.
- Keep PRs focused. One fix or feature per PR.
- Document what your script installs and any non-obvious decisions in the corresponding JSON metadata file.
+- **New scripts go to [DevScripts](https://github.com/community-scripts/DevScripts), not here.** PRs adding new scripts to this repository will be closed.
+- Keep a PR to one fix or one feature.
+- A bug that also happens on Incus is an application or engine bug — say so in the report.
+- Read the [Contributing Guidelines](CONTRIBUTING.md) before your first PR.

 ---

@@ -137,6 +191,8 @@ This project runs on community contributions. Whether you want to write new scri
        <sub><b>CrazyWolf13</b></sub>
      </a>
    </td>
+  </tr>
+  <tr>
    <td align="center">
      <a href="https://github.com/tremor021">
        <img src="https://github.com/tremor021.png" width="80" height="80" style="border-radius:50%" alt="tremor021" /><br/>
@@ -155,6 +211,7 @@ This project runs on community contributions. Whether you want to write new scri
        <sub><b>asylumexp</b></sub>
      </a>
    </td>
+    <td></td>
  </tr>
 </table>

@@ -194,9 +251,11 @@ This project runs on community contributions. Whether you want to write new scri

 ## Support the Project

-This project is maintained by volunteers. All infrastructure costs come out of pocket, and the work is done in people's spare time.
+This project is maintained by volunteers. Infrastructure costs come out of
+pocket and the work happens in people's spare time.

-**30% of all donations are forwarded directly to cancer research and hospice care** — a cause that was important to tteck.
+**30% of all donations are forwarded directly to cancer research and hospice
+care** — a cause that was important to tteck.

 <div align="center">
  <a href="https://ko-fi.com/community_scripts">
@@ -212,14 +271,13 @@ This project is maintained by volunteers. All infrastructure costs come out of p

 ## License

-This project is licensed under the [MIT License](LICENSE) — free to use, modify, and redistribute for personal and commercial purposes.
-
-See the full license text in [LICENSE](LICENSE).
+MIT — free to use, modify and redistribute, for personal and commercial
+purposes. See [LICENSE](LICENSE).

 ---

 <div align="center">
  <sub>Built on the foundation of <a href="https://github.com/tteck">tteck</a>'s original work · <a href="https://github.com/tteck/Proxmox">Original Repository</a></sub><br/>
  <sub>Maintained and expanded by the community · In memory of tteck</sub><br/>
-  <sub><i>Proxmox® is a registered trademark of <a href="https://www.proxmox.com/en/about/company">Proxmox Server Solutions GmbH</a></i></sub>
+  <sub><i>This is an independent community project. <b>Proxmox</b>® is a registered trademark of <a href="https://www.proxmox.com/en/about/company">Proxmox Server Solutions GmbH</a>.</i></sub>
 </div>
@@ -22,40 +22,18 @@ color
 catch_errors

 function update_script() {
-  header_info
-  check_container_storage
-  check_container_resources
-  if [[ ! -d /opt/meshcentral ]]; then
-    msg_error "No ${APP} Installation Found!"
-    exit
-  fi
-
-  NODE_VERSION="24" setup_nodejs
-
-  CURRENT=$(node -p "require('/opt/meshcentral/node_modules/meshcentral/package.json').version" 2>/dev/null)
-  LATEST=$(npm view meshcentral version 2>/dev/null)
-  if [[ -z "$LATEST" ]]; then
-    msg_error "Could not determine the latest MeshCentral version from npm"
-    exit 250
-  fi
-  if [[ "$CURRENT" != "$LATEST" ]]; then
-    msg_info "Stopping Service"
-    systemctl stop meshcentral
-    msg_ok "Stopped Service"
-
-    msg_info "Updating ${APP} from v${CURRENT} to v${LATEST}"
-    cd /opt/meshcentral
-    $STD npm install "meshcentral@${LATEST}"
-    msg_ok "Updated ${APP} to v${LATEST}"
-
-    msg_info "Starting Service"
-    systemctl start meshcentral
-    msg_ok "Started Service"
+    header_info
+    check_container_storage
+    check_container_resources
+    if [[ ! -d /opt/meshcentral ]]; then
+        msg_error "No ${APP} Installation Found!"
+        exit
+    fi
+    msg_info "Updating ${APP} LXC"
+    apt_update_safe
+    $STD apt -y upgrade
    msg_ok "Updated successfully!"
-  else
-    msg_ok "${APP} is already at v${CURRENT}"
-  fi
-  exit
+    exit
 }

 start
@@ -92,7 +92,7 @@ $STD /opt/splunk/bin/splunk enable boot-start \
    --no-prompt
 chown -R splunk:splunk /opt/splunk
 $STD systemctl daemon-reload
-$STD systemctl enable --now splunkd
+$STD systemctl enable --now Splunkd
 msg_ok "Started Service"

 motd_ssh
@@ -0,0 +1,15 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" role="img" aria-labelledby="title desc">
+  <title id="title">Community Scripts - CS Amber</title>
+  <desc id="desc">A continuous ivory C interlocks with a warm orange S on charcoal. Both letterforms use rounded, folded geometry.</desc>
+  <rect width="512" height="512" rx="112" fill="#29262b"/>
+  <defs>
+    <mask id="weave-clearance" maskUnits="userSpaceOnUse" x="0" y="0" width="512" height="512">
+      <rect width="512" height="512" fill="white"/>
+      <path d="M390 142H322L270 172V220L322 250H348L392 276V338L338 370H284" fill="none" stroke="black" stroke-width="72" stroke-linecap="round" stroke-linejoin="round"/>
+    </mask>
+  </defs>
+  <g fill="none" stroke-width="56" stroke-linecap="round" stroke-linejoin="round">
+    <path d="M254 142H186L118 182V330L186 370H254" stroke="#f5f4eb" mask="url(#weave-clearance)"/>
+    <path d="M390 142H322L270 172V220L322 250H348L392 276V338L338 370H284" stroke="#f29a67"/>
+  </g>
+</svg>
@@ -149,7 +149,7 @@ rm -f "$FILE_IMG"
 msg_info "Attaching EFI and root disk"
 qm set $VMID \
  --efidisk0 ${STORAGE}:0,efitype=4m \
-  --scsi0 ${DISK_REF},${DISK_CACHE}ssd=1,discard=on \
+  --scsi0 ${DISK_REF},ssd=1,discard=on \
  --boot order=scsi0 \
  --serial0 socket >/dev/null
 qm set $VMID --agent enabled=1 >/dev/null
@@ -201,12 +201,12 @@ DISK_REF="${STORAGE}:${DISK_REF:-}${DISK_VAR:-}"

 msg_ok "Extracted Mikrotik RouterOS CHR Disk Image"
 msg_info "Creating Mikrotik RouterOS CHR VM"
-qm create $VMID${MACHINE} -tablet 0 -localtime 1${CPU_TYPE} -cores $CORE_COUNT -memory $RAM_SIZE -name $HN \
+qm create $VMID -tablet 0 -localtime 1 -cores $CORE_COUNT -memory $RAM_SIZE -name $HN \
  -tags community-script -net0 virtio,bridge=$BRG,macaddr=$MAC$VLAN$MTU \
  -onboot 1 -ostype l26 -scsihw virtio-scsi-pci
 qm importdisk $VMID "$FILE" $STORAGE ${DISK_IMPORT:-} 1>&/dev/null
 qm set $VMID \
-  -scsi0 "${DISK_REF},${DISK_CACHE}${THIN%,}" \
+  -scsi0 "$DISK_REF" \
  -boot order=scsi0 >/dev/null

 set_description
@@ -161,7 +161,7 @@ msg_info "Creating TrueNAS VM shell"
 qm create "$VMID"${MACHINE} -bios ovmf -agent enabled=1 -tablet 0 -localtime 1${CPU_TYPE} \
  -cores "$CORE_COUNT" -memory "$RAM_SIZE" -balloon 0 -name "$HN" -tags community-script \
  -net0 "virtio,bridge=$BRG,macaddr=$MAC$VLAN$MTU" -onboot 1 -ostype l26 \
-  -efidisk0 $STORAGE:1,efitype=4m,pre-enrolled-keys=0 -sata0 ${STORAGE}:${DISK_SIZE%G},${DISK_CACHE}ssd=1 \
+  -efidisk0 $STORAGE:1,efitype=4m,pre-enrolled-keys=0 -sata0 ${STORAGE}:${DISK_SIZE%G},ssd=1 \
  -scsihw virtio-scsi-single -cdrom "$ISO_VOLUME" -boot order='sata0;ide2' -vga virtio >/dev/null
 msg_ok "Created VM shell"

@@ -374,7 +374,7 @@ vm_import_disk "$VMID" "$FILE" "$STORAGE" "$DISK_IMPORT_FORMAT"

 qm set "$VMID" \
  -efidisk0 "${STORAGE}:0,efitype=4m" \
-  -scsi0 "${VM_IMPORTED_DISK},${DISK_CACHE}${THIN}size=${DISK_SIZE}" \
+  -scsi0 "${VM_IMPORTED_DISK},${DISK_CACHE}size=${DISK_SIZE}" \
  -boot order=scsi0 -serial0 socket >/dev/null
 vm_resize_disk
 qm set "$VMID" --agent enabled=1 >/dev/null
Author	SHA1	Message	Date
CanbiZ (MickLesk)	3d039ca8e8	Update script count from 600 to 700 in README	2026-10-26 10:44:19 +01:00
MickLesk	2d4b7b669b	Say how an update is actually run, and show the fork case first The update block told people to reach the container with pct, which is not how anyone gets there; the website says to type "update" in the container console, so say that. VM scripts have no updater at all, which the page did not mention. The fork example exported the core URL, which only matters when the engine itself is being changed -- the ordinary case is a fork of the scripts, and it needs COMMUNITY_SCRIPTS_URL or the engine looks for the install half upstream. Neither needs exporting.	2026-10-26 10:41:19 +01:00
MickLesk	a7f39fb710	Refresh the brand assets and drop the json/ line from CONTRIBUTING core archived these two files as old_logo* a fortnight ago and Incus carries the current artwork, so this repository was the last one still serving the 2023 logo -- to the Argus icon, the Discord hook example and the owncloud VM description, all of which now follow without a change. CONTRIBUTING said metadata is managed on the website and, one line below, pointed at a json/ directory that no longer exists.	2026-10-26 10:37:33 +01:00
MickLesk	10c009a7bc	Rebuild the README around the new brand and the repository split The header carried the 2023 logo while core and Incus had moved to the current artwork, and the page never said that the scripts here are only half the story -- the engine lives in core and the same scripts run on Incus. It also listed four Proxmox versions where pve_check accepts two ranges, and pointed contributors at a json/ directory that no longer exists. Adds the repository map, the folder layout, how to run a fork or branch, the update command and a note that these commands run as root. Drops the category table, which duplicated the website and drifted from it.	2026-10-26 10:35:06 +01:00
MickLesk	a44f2f5871	Use the vector logo in the README and state the versions the engine accepts The header still carried the 2023 raster logo, which is soft on any display above 1x. The requirements table named four Proxmox versions where pve_check accepts two ranges, so 8.0 through 8.3 read as unsupported and every new release would need an edit here.	2026-10-26 10:27:13 +01:00