2025-11-02 23:49:54 -08:00
|
|
|
#!/usr/bin/env bash
|
2025-04-01 10:25:46 +02:00
|
|
|
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func)
|
2026-01-06 13:28:12 +01:00
|
|
|
# Copyright (c) 2021-2026 community-scripts ORG
|
2026-01-29 10:58:41 +01:00
|
|
|
# Author: MickLesk (Canbiz) | Co-Author: CrazyWolf13
|
2024-12-16 12:42:51 +01:00
|
|
|
# License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE
|
several scripts: add additional github link in source (#12282)
* fix(error-handler): prevent silent() from re-enabling error handling during recovery
Root cause: silent() (core.func) unconditionally calls set -Eeuo pipefail
and trap 'error_handler' ERR after every command. When build_container()
intentionally disables error handling for its recovery section, any
intermediate call through silent()/ re-enables it. This causes the
grep/sed pipeline for missing_cmd extraction to trigger error_handler
(grep returns exit code 1 on no match + pipefail = fatal).
Fixes:
1. silent(): Save errexit state before disabling, only restore if it was
active. Callers that intentionally disabled error handling (e.g.
build_container recovery) are no longer silently re-enabled.
2. build.func: Add || true to missing_cmd grep pipeline as defense-in-depth
against pipeline failure propagation.
3. build.func: Add explicit set +Eeuo pipefail / trap - ERR after
post_update_to_api() call, before error classification grep/sed section.
4. build.func: Remove stale global combined_log variable from variables()
that used a different path format (/tmp/install-SESSION-combined.log)
than the actual local variable (/tmp/NSAPP-CTID-SESSION.log). The global
was never written to and caused confusion when error_handler displayed it.
* Update build.func
* chore(install): add Github source links to all setup_nodejs scripts
52 install scripts had a project website in '# Source:' but no GitHub
link. Merged the GitHub repo URL into the Source header as:
# Source: https://website.com/ | Github: https://github.com/OWNER/REPO
Repos sourced from fetch_and_deploy_gh_release calls, get_latest_github_release
calls, or known project repos for npm/pip installed apps.
Two scripts (fumadocs, pve-scripts-local) had no Source line at all —
added one. Shinobi skipped (GitLab-only, no GitHub repo).
* chore(install): add Github source links to all fetch_and_deploy scripts
77 additional install scripts had fetch_and_deploy_gh_release calls but
no GitHub link in the Source header. Merged the primary app repo into
the Source header as:
# Source: https://website.com/ | Github: https://github.com/OWNER/REPO
Where multiple fetch_and_deploy calls existed (app + dependency), the
primary app repo was selected:
- ersatztv: ErsatzTV/ErsatzTV (not ffmpeg)
- firefly: firefly-iii/firefly-iii (not data-importer)
- komga: gotson/komga (not kepubify dep)
- sabnzbd: sabnzbd/sabnzbd (not par2cmdline-turbo dep)
- signoz: SigNoz/signoz (not otel-collector)
- tunarr: chrisbenincasa/tunarr (not ffmpeg dep)
Also fixed cosmos-install.sh double https:// in Source URL.
Skipped: autocaliweb (source already on codeberg, GitHub repos are deps only)
* revert: restore misc/build.func and misc/core.func to main state
These error-handler fixes belong to fix/error-handler-recovery, not to
this sources-only branch.
* chore(ct,tools): sync Source headers with install/ and add Github links to addon scripts
2026-02-24 15:11:53 +01:00
|
|
|
# Source: https://vikunja.io/ | Github: https://github.com/go-vikunja/vikunja
|
2024-11-05 23:57:28 +01:00
|
|
|
|
|
|
|
|
APP="Vikunja"
|
2025-04-10 11:56:52 +02:00
|
|
|
var_tags="${var_tags:-todo-app}"
|
|
|
|
|
var_cpu="${var_cpu:-1}"
|
|
|
|
|
var_ram="${var_ram:-1024}"
|
|
|
|
|
var_disk="${var_disk:-4}"
|
|
|
|
|
var_os="${var_os:-debian}"
|
2025-10-07 21:40:31 +02:00
|
|
|
var_version="${var_version:-13}"
|
2025-04-10 11:56:52 +02:00
|
|
|
var_unprivileged="${var_unprivileged:-1}"
|
2024-12-16 12:42:51 +01:00
|
|
|
|
|
|
|
|
header_info "$APP"
|
2024-11-05 23:57:28 +01:00
|
|
|
variables
|
|
|
|
|
color
|
|
|
|
|
catch_errors
|
|
|
|
|
|
|
|
|
|
function update_script() {
|
2024-12-16 12:42:51 +01:00
|
|
|
header_info
|
|
|
|
|
check_container_storage
|
|
|
|
|
check_container_resources
|
|
|
|
|
if [[ ! -d /opt/vikunja ]]; then
|
|
|
|
|
msg_error "No ${APP} Installation Found!"
|
|
|
|
|
exit
|
|
|
|
|
fi
|
2026-01-29 10:58:41 +01:00
|
|
|
|
|
|
|
|
RELEASE="$( [[ -f "$HOME/.vikunja" ]] && cat "$HOME/.vikunja" 2>/dev/null || [[ -f /opt/Vikunja_version ]] && cat /opt/Vikunja_version 2>/dev/null || true)"
|
|
|
|
|
if [[ -z "$RELEASE" ]] || [[ "$RELEASE" == "unstable" ]] || dpkg --compare-versions "${RELEASE:-0.0.0}" lt "1.0.0"; then
|
|
|
|
|
msg_warn "You are upgrading from Vikunja '$RELEASE'."
|
|
|
|
|
msg_warn "This requires MANUAL config changes in /etc/vikunja/config.yml."
|
|
|
|
|
msg_warn "See: https://vikunja.io/changelog/whats-new-in-vikunja-1.0.0/#config-changes"
|
|
|
|
|
|
2026-03-02 13:57:42 +01:00
|
|
|
read -rp "Continue with update? (y to proceed): " -t 30 CONFIRM1 || exit 254
|
2026-01-29 10:58:41 +01:00
|
|
|
[[ "$CONFIRM1" =~ ^[yY]$ ]] || exit 0
|
|
|
|
|
|
|
|
|
|
echo
|
|
|
|
|
msg_warn "Vikunja may not start after the update until you manually adjust the config."
|
|
|
|
|
msg_warn "Details: https://vikunja.io/changelog/whats-new-in-vikunja-1.0.0/#config-changes"
|
|
|
|
|
|
2026-03-02 13:57:42 +01:00
|
|
|
read -rp "Acknowledge and continue? (y): " -t 30 CONFIRM2 || exit 254
|
2026-01-29 10:58:41 +01:00
|
|
|
[[ "$CONFIRM2" =~ ^[yY]$ ]] || exit 0
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
if check_for_gh_release "vikunja" "go-vikunja/vikunja"; then
|
2026-01-29 12:43:54 +01:00
|
|
|
echo
|
|
|
|
|
msg_warn "The package update may include config file changes."
|
|
|
|
|
echo -e "${TAB}${YW}How do you want to handle /etc/vikunja/config.yml?${CL}"
|
|
|
|
|
echo -e "${TAB} 1) Keep your current config"
|
|
|
|
|
echo -e "${TAB} 2) Install the new package maintainer's config"
|
|
|
|
|
read -rp " Choose [1/2] (default: 1): " -t 60 CONFIG_CHOICE || CONFIG_CHOICE="1"
|
|
|
|
|
[[ -z "$CONFIG_CHOICE" ]] && CONFIG_CHOICE="1"
|
|
|
|
|
|
|
|
|
|
if [[ "$CONFIG_CHOICE" == "2" ]]; then
|
|
|
|
|
export DPKG_FORCE_CONFNEW="1"
|
|
|
|
|
else
|
|
|
|
|
export DPKG_FORCE_CONFOLD="1"
|
|
|
|
|
fi
|
|
|
|
|
|
2025-10-07 21:40:31 +02:00
|
|
|
msg_info "Stopping Service"
|
2024-12-16 12:42:51 +01:00
|
|
|
systemctl stop vikunja
|
2025-10-07 21:40:31 +02:00
|
|
|
msg_ok "Stopped Service"
|
2024-11-05 23:57:28 +01:00
|
|
|
|
2026-01-29 10:58:41 +01:00
|
|
|
fetch_and_deploy_gh_release "vikunja" "go-vikunja/vikunja" "binary"
|
2026-02-25 18:27:11 +01:00
|
|
|
$STD systemctl daemon-reload
|
2024-11-05 23:57:28 +01:00
|
|
|
|
2025-10-07 21:40:31 +02:00
|
|
|
msg_info "Starting Service"
|
2024-12-16 12:42:51 +01:00
|
|
|
systemctl start vikunja
|
2025-10-07 21:40:31 +02:00
|
|
|
msg_ok "Started Service"
|
2025-10-30 09:24:16 -07:00
|
|
|
msg_ok "Updated successfully!"
|
2024-12-16 12:42:51 +01:00
|
|
|
fi
|
2026-01-29 10:58:41 +01:00
|
|
|
exit 0
|
2024-11-05 23:57:28 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
start
|
|
|
|
|
build_container
|
|
|
|
|
description
|
|
|
|
|
|
2026-01-06 22:57:40 +01:00
|
|
|
msg_ok "Completed successfully!\n"
|
2024-12-16 12:42:51 +01:00
|
|
|
echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"
|
|
|
|
|
echo -e "${INFO}${YW} Access it using the following URL:${CL}"
|
2025-04-01 10:51:52 +02:00
|
|
|
echo -e "${TAB}${GATEWAY}${BGN}http://${IP}:3456${CL}"
|