feat: initial upload

Author: wandercone

LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2026 wandercone
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
+DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
+OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
+OR OTHER DEALINGS IN THE SOFTWARE.

LICENSE-unraid-plugin-template

@@ -1,187 +1,34 @@
-# Unraid Plugin Template
+# Unraid-Sidegrade
 
-A simple template to help you create your own Unraid plugin, even if you're new to development.
+An unofficial Unraid OS updater. Paste a download URL, verify the checksum, reboot. Bypasses the official update flow and installs any OS version directly to the boot device.
 
-## What You'll Need
+## Features
 
-📝 **Requirements:**
+- Install any Unraid OS version from a direct download URL
+- MD5 checksum verification before touching the boot device
+- Automatic backup of current boot files to `/boot/previous`
 
-- A GitHub account
-- Basic understanding of Unraid
-- Text editor (VS Code is recommended for beginners)
-- Your Unraid server for testing
+## Requirements
 
----
+- Unraid 7.0.0 or later
 
-## Getting Started
+## Installation
 
-### 📁 Step 1: Create Your Plugin Repository
+**Via Plugin URL**
 
-1. Click the green "Use this template" button at the top of this page
-2. Give your new repository a name (this will be your plugin's name)
-3. Make it public so others can use your plugin
-4. Click "Create repository from template"
+1. In the Unraid UI go to **Plugins > Install Plugin**
+2. Paste the `.plg` URL from the [latest release](https://raw.githubusercontent.com/wandercone/Updater/refs/heads/main/plugin/updater.plg)
+3. Click **Install**
 
-### ✏️ Step 2: Customize Your Plugin
+After installation the plugin is available at **System Information > Unraid Updater**.
 
-2. Customize the template:
-   - **Option A: Automated**
-     - Run the `customize.sh` script to download and run the customization tool:
-       ```sh
-       ./customize.sh
-       ```
-   - **Option B: Manual**
-     - Follow the customization guide below to customize the template files yourself.
+## Usage
 
-### ⚙️ Step 3: Enable GitHub Actions
+1. Visit the [Unraid version history](https://docs.unraid.net/unraid-os/download_list/) and copy the download URL and MD5 checksum for the version you want
+2. Paste the URL and checksum into the plugin
+3. Click Download & Install
+4. Reboot
 
-In your GitHub repository settings, make sure "Actions" are enabled. This is **required** for the release workflow to automatically build your plugin packages when you create releases. Without this, users won't be able to install your plugin.
+## How It Works
 
-### 🚀 Step 4: Test and Release
-
-Once you've made your changes, you can test your plugin and release it for others to use.
-
----
-
-## Publishing Your Plugin
-
-📦 **Release & Distribution**
-
-To release your plugin for others to use, you'll create a "release" on GitHub. This packages everything up into a file that Unraid can install.
-
-### How to Create a Release
-
-1. Go to your GitHub repository
-2. Click "Releases" (on the right side of the page)
-3. Click "Create a new release"
-4. Fill out the release form:
-   - **Tag**: Use your plugin version number (like `2025.01.15`)
-   - **Release title**: Use the same version number
-   - **Description**: Explain what your plugin does or what changed in this version
-
-### Version Numbers - Important!
-
-🔢 Use the Unraid convention of YYYY.MM.DD format like `2025.01.15`, `2025.01.16`, `2025.02.01`.
-
-If you need multiple releases on the same day, just add another number at the end.
-
-❌ **Don't use letters in version numbers:**
-
-- `2025.01.01a` ← This won't work properly
-- `2025.01.01b` ← This won't work properly
-
-✅ **Use numbers only:**
-
-- `2025.01.01.1` ← This works great
-- `2025.01.01.2` ← This works great
-
----
-
-## Code Quality and Testing (Recommended)
-
-🧪 **Quality & Testing Tools**
-
-The template includes several helpful tools to ensure your plugin works well and avoid hard-to-find bugs:
-
-- 🕵️‍♂️ **phpstan**: Checks your PHP code for potential bugs before you test it - catches issues that might not show up during testing
-- 🧹 **php-cs-fixer**: Automatically fixes coding style issues to keep your code clean and maintainable
-- 📝 **commitlint**: Ensures your commit messages follow a consistent format
-
-### Why Use These Tools?
-
-These tools help you catch bugs early and keep your code maintainable as your plugin grows. Many issues they find are subtle and might not appear during testing but could cause problems for users later.
-
-### Automatic Checks
-
-⚡ These tools run automatically whenever you upload changes to GitHub, providing an extra safety net.
-
-### Running Checks Manually
-
-You can also check your code locally before uploading:
-
-```bash
-# Install the tools (run this once)
-composer update
-
-# Check for potential bugs
-vendor/bin/phpstan analyse
-
-# Fix code formatting
-vendor/bin/php-cs-fixer fix
-```
-
-### Adjusting Tool Settings
-
-If phpstan finds too many issues and feels overwhelming:
-
-- You can lower the strictness level in `phpstan.neon` (change `level: 9` to a lower number like `level: 6`)
-- Work on fixing issues gradually rather than disabling the tools entirely
-
-### Customizing or Disabling Checks
-
-While it is recommended to keep these tools enabled:
-
-- To disable any checks: Remove them from `.github/workflows/lint.yml`
-- To adjust settings: Modify the configuration files:
-  - `phpstan.neon`: Bug detection settings
-  - `.php-cs-fixer.dist.php`: Code formatting rules
-  - `commitlint.config.js`: Commit message rules
-
----
-
-## Customization Guide (Manual Method)
-
-🛠️ **Customization Steps**
-
-Now that you have your own copy of the template, you need to customize it for your specific plugin. Here are the essential files to modify:
-
-### 1. Basic Plugin Information
-
-📄 **File: `plugin/plugin.json`**
-This file contains your plugin's basic information that Unraid uses. You must update these fields:
-
-- **name**: This becomes the filename for your .plg file. It's not the name users see, but the internal name for your plugin.
-- **package_name**: The internal package name. This is used by Slackware to identify your plugin. Recommendation: use `unraid-pluginname` (replace `pluginname` with your plugin's name) to avoid conflicts with upstream packages.
-- **author**: Your name or organization
-- **support**: URL where users can get help (typically a thread on the Unraid forums)
-- **launch**: Either update with your plugin's page path or remove if your plugin doesn't have a web interface
-- **icon**: Either use a Font Awesome 4.7.0 icon name, or remove this field and provide your own icon at `src/usr/local/emhttp/plugins/plugin-name/name.png` (where "name" matches the name field)
-
-📄 **File: `README.md` (this file)**
-Replace this template content with information about your plugin. This appears on your GitHub page and helps users understand what your plugin does.
-
-### 2. Plugin Description (What Users See During Installation)
-
-📝 **File: `src/install/slack-desc`**
-This is what users see when your plugin is being installed. Think of it as a brief advertisement for your plugin.
-
-**Important rules:**
-
-- Keep exactly 11 lines of description (plus the ruler line at the top)
-- Replace `my-plugin` with your package name (from `plugin.json`)
-- Adjust the handy ruler line (the line of dashes) so it lines up with the colon after your package name - this shows the maximum length for each description line
-
-### 3. Plugin Interface Files
-
-📁 **Folder: `src/usr/local/emhttp/plugins/plugin-name`**
-
-- Rename this folder to match your plugin's name from `plugin.json`
-- This folder contains the web interface files that appear in Unraid's web UI
-
-📄 **File: `src/usr/local/emhttp/plugins/plugin-name/README.md`**
-Update this with your plugin's name and what it does. This appears on Unraid's Plugins page.
-
-### 4. Optional: Diagnostic Information
-
-🩺 **File: `src/usr/local/emhttp/plugins/plugin-name/diagnostics.json.example`**
-This helps with troubleshooting your plugin. You can:
-
-- Rename it to `diagnostics.json` to enable custom diagnostic checks
-- Update the content to include your plugin's name and specific diagnostic checks
-- For detailed information on the diagnostics format, see: https://github.com/dkaser/unraid-plugin-diagnostics
-- Leave it as `.example` if you don't need custom diagnostics
-
-### 5. Legal Stuff
-
-⚖️ **File: `LICENSE`**
-The template uses "Unlicense" (public domain) so you can choose any license you want for your project. You can change this to any license you prefer. You should always include a license file in your repository to clarify how others can use your code.
+The install process follows the [official manual upgrade steps](https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/upgrading-unraid/)

README.md

@@ -1,7 +1,7 @@
 <?xml version='1.0' standalone='yes'?>
 <!DOCTYPE PLUGIN>
 
-<PLUGIN 
+<PLUGIN
   name="{{ name }}"
   author="{{ author }}"
   version="{{ env['PLUGIN_VERSION'] }}"

customize.sh

@@ -1,9 +1,8 @@
 {
-    "name": "plugin-name",
-    "package_name": "my-plugin",
-    "author": "Your Name",
-    "min": "7.0.0",
-    "icon": "question",
-    "support": "https://...",
-    "launch": "Tools/Something"
-}
+  "name": "updater",
+  "package_name": "updater",
+  "author": "wandercone",
+  "support": "https://github.com/wandercone/Updater/issues",
+  "launch": "Tools/Updater",
+  "icon": "cloud-download "
+}

plugin/plugin.j2

@@ -0,0 +1,69 @@
+<?xml version='1.0' standalone='yes'?>
+<!DOCTYPE PLUGIN>
+
+<PLUGIN
+  name="updater"
+  author="wandercone"
+  version="2026.03.31"
+  launch="Tools/Updater"
+  pluginURL="https://raw.githubusercontent.com/wandercone/Updater/main/plugin/updater.plg"
+  support="https://github.com/wandercone/Updater/issues"
+  
+  
+  icon="cloud-download "
+>
+
+<CHANGES>
+<![CDATA[
+
+### 2026.03.31
+
+- chore: address php-cs-fixer comments
+- feat: initial upload
+
+
+For older releases, see https://github.com/wandercone/Updater/releases
+]]>
+</CHANGES>
+
+<FILE Name="/boot/config/plugins/updater/updater-2026.03.31-noarch-1.txz">
+<URL>https://github.com/wandercone/Updater/releases/download/2026.03.31/updater-2026.03.31-noarch-1.txz</URL>
+<SHA256>5e497e5c409d6dd184f524b70287a430f2d222ac2888ddcf922af56e2968c2e2</SHA256>
+</FILE>
+
+<!--
+The 'install' script.
+-->
+<FILE Run="/bin/bash">
+<INLINE>
+<![CDATA[
+upgradepkg --install-new /boot/config/plugins/updater/updater-2026.03.31-noarch-1.txz
+
+# cleanup old versions
+rm -f $(ls /boot/config/plugins/updater/updater-*.txz 2>/dev/null | grep -v '2026.03.31')
+
+echo ""
+echo "----------------------------------------------------"
+echo " updater has been installed."
+echo " Version: 2026.03.31"
+echo "----------------------------------------------------"
+echo ""
+]]>
+</INLINE>
+</FILE>
+
+<!--
+The 'remove' script.
+-->
+<FILE Run="/bin/bash" Method="remove">
+<INLINE>
+<![CDATA[
+removepkg updater
+
+rm -rf /usr/local/emhttp/plugins/updater
+rm -rf /boot/config/plugins/updater
+]]>
+</INLINE>
+</FILE>
+
+</PLUGIN>

plugin/plugin.json

@@ -1,12 +1,9 @@
          |-----handy-ruler------------------------------------------------------|
-my-plugin: my-plugin
-my-plugin:
-my-plugin: Sample slack-desc file
-my-plugin:
-my-plugin:
-my-plugin:
-my-plugin:
-my-plugin:
-my-plugin:
-my-plugin: https://github.com/my-user/my-plugin
-my-plugin:
+updater: updater
+updater:
+updater: An unofficial Unraid updater plugin.
+updater: Fetches a manual specified releases and installs is via the 
+updater: documented manual upgrade process.
+updater:
+updater: https://github.com/wandercone/Updater
+updater: