2d24a764a8
Two mechanical sweeps, no behaviour change on a single-root install. The 14 `[[ "$p" == "$containers_dir"* ]]` prefix tests that decide manager-vs-container-user elevation become pathIsContainerData, so a file on a second storage root is no longer misclassified as manager-owned — which would have written it with the wrong owner and failed later, far from the cause. The 65 references to the WebUI's own tree become webuiDir(), which is pinned to the primary root by design. Two traps found while doing it: run_privileged.sh is sourced directly by init.sh without paths.sh, so it needs a fallback. Defining one named pathIsContainerData was wrong: generate_function_manifest.sh indexes top-level definitions, and the resulting autoload stub would have shadowed the real multi-root implementation with the primary-only fallback — silently classifying every file on a second disk as manager-owned, which is exactly the bug this sweep exists to prevent. Renamed to _runCfgIsContainerPath, which delegates when the real one is loaded. setup_lock.sh built its path in a top-level assignment, so it was evaluated at source time and needed the file flagged eager. Made it a function instead: the path resolves on call, and the file drops off LP_EAGER_FILES entirely. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 lines
271 B
Bash
Executable File
13 lines
271 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# LibrePortal WebUI Setup Lock Removal
|
|
# Removes setup lock file after update completion
|
|
|
|
webuiRemoveSetupLock() {
|
|
local lock_file="$(webuiDir)/frontend/data/setup.lock"
|
|
|
|
if [ -f "$lock_file" ]; then
|
|
runFileOp rm -f "$lock_file"
|
|
fi
|
|
}
|