534f179ee6
main was 16 days and 259 commits behind the line the product is actually built on, at contract 0.30.0 against 0.35.0, with no per-PC credential code at all. It was neither current nor curated - just stale. This brings it forward and, at the same time, makes it mean something: main is what a receiving site installs, and nothing else. WHAT IT CARRIES. Twelve plugins - backups, computers, endpoints, guides, knowledgebase, machines, network, notifications, printers, slides, tools, warranty - plus applications, which is manifest-less core and always ships. The only manifest dependency inside that set is endpoints on computers, and both are in it, so the closure is self-contained. WHAT IT DOES NOT. employees, geenforce, measuringtools, printedparts and usb stay on the site line. So do the Windows installer tree, the VM rehearsal helpers, the agent tooling config, one site's data loader, the internal audit and findings records, and the planner spreadsheet. 1,135 tracked files against 1,438. A REMOVAL THAT BREAKS THE APP IS NOT A REMOVAL, and two nearly shipped: deploy/site-profile-universal.json still named all seventeen plugins. It is the file docs/DEPLOY.md tells a site to provision from, so a fresh install would have failed at `flask plugin apply-profile` with PluginError - the first thing a receiving site does, broken by the branch meant to serve them. It now names the twelve that exist, and its comment says the two must agree. agent/ was never refreshed. Whoever populated this branch copied shopdb/, plugins/, frontend/ and tests/ from the site line and left the agent tree at its September state: 22 C# and PowerShell sources missing, including AgentCredentials, EnrollmentService, AgentHttpFactory and the fleet-alert client, plus one file the site line had deleted still present. The old tree is internally consistent, so it compiles, and nothing in CI builds it - every gate was green over a server that speaks enrollment and per-PC credentials to a bundled agent source that cannot. Resynced whole. DECISIONS THIS ENCODES, rather than defers: - The plugin-authoring lab builds printedparts, whose manifest depends on employees, so it could not stay. The lab remains on the site line and main ships no build-along tutorial. That is a real loss for an adopting developer and is recorded here rather than discovered later. - Recognition, Training and Recertification notifications are no longer seeded. Each splits one notification into a card per employee and renders a photo, which needs a plugin this branch does not bundle. Seeding them would offer an author a type that cannot resolve anybody. A site that installs employees gets them from that plugin's own seed. - Windows/IIS is documented as the legacy path throughout, and the README leads with Docker, because that is what a receiving site gets. The API description is regenerated for THIS branch - 347 paths and 483 operations, down from 415 and 573 - so the published contract describes what is here rather than what the site line serves. docs/CONFIG.md lost the two measuring-tool label keys the code no longer declares, which two lanes had decided opposite ways. Suite: 3124 passed, 6 skipped. Naming and style gates pass. The docs gates run rather than skip, and every index line count is derived from the file it names.
62 lines
2.5 KiB
Bash
Executable File
62 lines
2.5 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# ShopDB backup WATCHER - the resident half of the in-app backup utility.
|
|
#
|
|
# WHY this exists: the api container cannot run docker, so when an operator
|
|
# clicks "Back up now" the api only drops a sentinel file (.backup-requested)
|
|
# on the shared backups volume. This watcher is the thing that actuates that
|
|
# request: it polls for the sentinel and runs the one-shot backup.sh, which
|
|
# ships a restic snapshot to the backup-store container and clears the sentinel
|
|
# on success. That turns the UI button into a real, self-serve backup without
|
|
# giving the api container any docker or host privileges.
|
|
#
|
|
# ASCII only, no emojis - matches the repo style gate.
|
|
set -uo pipefail
|
|
|
|
BACKUPS_ROOT="${SHOPDB_BACKUPS_ROOT:-/backups}"
|
|
SENTINEL="${BACKUPS_ROOT}/.backup-requested"
|
|
RESTORE_SENTINEL="${BACKUPS_ROOT}/.restore-requested"
|
|
INTERVAL="${BACKUP_POLL_SECONDS:-10}"
|
|
|
|
log() { echo "[backup-watch] $*"; }
|
|
|
|
# shellcheck source=scripts/backup/status.sh
|
|
. /opt/backup/status.sh
|
|
|
|
mkdir -p "${BACKUPS_ROOT}"
|
|
# The api container runs unprivileged and only drops sentinel files here; it
|
|
# cannot write into a root-owned 0755 directory. Make the backups root
|
|
# writable so "Back up now" and "Restore" can queue their sentinels.
|
|
chmod 0777 "${BACKUPS_ROOT}" 2>/dev/null || true
|
|
log "watcher up; polling ${SENTINEL} and ${RESTORE_SENTINEL} every ${INTERVAL}s"
|
|
|
|
while true; do
|
|
if [ -f "${SENTINEL}" ]; then
|
|
log "backup requested - running one-shot"
|
|
status_write backup queued "" "Backup queued"
|
|
if /opt/backup/backup.sh; then
|
|
log "backup completed"
|
|
else
|
|
# backup.sh only clears the sentinel on success, so a failed run
|
|
# would otherwise loop forever. Clear it here and wait for the next
|
|
# explicit request rather than hammering a broken backup.
|
|
log "backup FAILED - clearing request, awaiting next"
|
|
rm -f "${SENTINEL}" 2>/dev/null || true
|
|
fi
|
|
fi
|
|
if [ -f "${RESTORE_SENTINEL}" ]; then
|
|
# The api drops the target set name into the restore sentinel. Read it,
|
|
# hand it to restore.sh, and clear the request whether it succeeds or
|
|
# fails so a bad set cannot pin the watcher in a tight retry loop.
|
|
setname="$(head -n1 "${RESTORE_SENTINEL}" 2>/dev/null | tr -d '\r\n')"
|
|
log "restore requested - running restore for ${setname}"
|
|
status_write restore queued "${setname}" "Restore queued"
|
|
if /opt/backup/restore.sh "${setname}"; then
|
|
log "restore completed"
|
|
else
|
|
log "restore FAILED - clearing request, awaiting next"
|
|
fi
|
|
rm -f "${RESTORE_SENTINEL}" 2>/dev/null || true
|
|
fi
|
|
sleep "${INTERVAL}"
|
|
done
|