Create non-destructive upgrade utility for comments functionality

[tim-moody]

• create database ugrade that adds any new tables and modifies any existing tables, preserving data
• write a script to apply a code patch to an instance of Calibre-Web installed in IIAB

[chapmanjacobd]

The changes already in cps/ub.py:

1. Add two new tables: VideoComments and VideoRatings

2. Includes migration logic in add_missing_tables() that checks if tables
   exist before creating them:

if not engine.dialect.has_table(engine.connect(), "video_comments"):
    VideoComments.__table__.create(bind=engine)

This is a non-destructive, additive change that follows the existing pattern used for archived_book and thumbnail tables.

The tables will be auto-created on application startup if they don't exist.

[chapmanjacobd]

For a code patch you could use git pull if the devices are networked (even without Internet access)

or git diff and git apply if only async access (thumb drive) is available

[chapmanjacobd]

#!/bin/bash
# Script to create a git patch file

set -e

if [ $# -lt 1 ]; then
    echo "Usage: $0 <patch_name> [commit_or_range]"
    echo ""
    echo "Examples:"
    echo "  $0 my_changes.patch              # Create patch from unstaged/staged changes"
    echo "  $0 my_changes.patch HEAD~1       # Create patch from last commit"
    echo "  $0 my_changes.patch main..feature # Create patch from branch range"
    exit 1
fi

PATCH_NAME="$1"
COMMIT_RANGE="${2:-}"

if [ -n "$COMMIT_RANGE" ]; then
    echo "Creating patch from: $COMMIT_RANGE"
    git diff "$COMMIT_RANGE" > "$PATCH_NAME"
else
    echo "Creating patch from current changes (staged + unstaged)"
    git diff > "$PATCH_NAME"
fi

echo "Patch created: $PATCH_NAME"
echo "Lines: $(wc -l < "$PATCH_NAME")"

Then you'll want to copy it somehow, either through network or USB. After copying to the next system you would run something like this:

#!/bin/bash
# Script to apply a git patch file

set -e

if [ $# -lt 1 ]; then
    echo "Usage: $0 <patch_file> [options]"
    echo ""
    echo "Options:"
    echo "  --check     Only check if patch can be applied (don't apply)"
    echo "  --reverse   Apply patch in reverse"
    echo "  --3way      Use 3-way merge if patch doesn't apply cleanly"
    echo ""
    echo "Examples:"
    echo "  $0 my_changes.patch        # Apply patch"
    echo "  $0 my_changes.patch --check # Check if patch applies"
    exit 1
fi

PATCH_FILE="$1"
shift

if [ ! -f "$PATCH_FILE" ]; then
    echo "Error: Patch file '$PATCH_FILE' not found"
    exit 1
fi

echo "Applying patch: $PATCH_FILE"

if [ "$1" = "--check" ]; then
    git apply --check "$PATCH_FILE"
elif [ "$1" = "--reverse" ]; then
    git apply -R "$PATCH_FILE"
elif [ "$1" = "--3way" ]; then
    git apply --3way "$PATCH_FILE"
else
    git apply "$PATCH_FILE"
fi

[chapmanjacobd]

But if the devices are networked, the semantics for ignoring all local changes and reverting to upstream are a bit clearer:

git fetch upstream
git reset --hard FETCH_HEAD

[tim-moody]

Most IIAB services that install from a repo do not use the repo directly but put its code somewhere else, library or opt. I was assuming calibreweb did the same, so that simply refreshing the repo would not be sufficient.

Ideally it would be nice if runrole calibre-web --reinstall was all that was required, especially since the database seems to be self-healing.

[chapmanjacobd]

Looks like we're still keeping around the .git folder which is good:

/usr/local/calibre-web-py3 (set by calibreweb_venv_path)

So sudo runrole calibre-web --reinstall should just work? Is git complaining that the folder already exists? Maybe we need to do something like this instead:

# cd /usr/local/calibre-web-py3 && git pull
# systemctl restart calibre-web

[GarbaJohnAshifa]

yes @chapmanjacobd , It works.