[freakms]

✍️ Description

Adds XWiki, an open source enterprise wiki (Confluence alternative), installed from the official XWiki Debian repository (maven.xwiki.org) with Tomcat 10 and OpenJDK 21 from Debian 13, and PostgreSQL (default) or MariaDB via var_xwiki_db=mariadb.
Deviation from the standard pattern: XWiki is distributed as signed .deb packages (database created by the package via dbconfig-common), so install and update_script use apt instead of fetch_and_deploy_gh_release; the update backs up /etc/xwiki to /opt and only upgrades installed xwiki-* packages.
Tested on Proxmox VE 9.2.26: install with PostgreSQL and with MariaDB, Distribution Wizard, update (existing pages kept), container reboot.

🔗 Related PR / Issue

Link: community-scripts/ProxmoxVE#12671

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🏗️ arm64 Support (X in brackets)

• arm64 supported - Tested and supported on arm64.
• arm64 not tested - Assumed to work on arm64, but testing has not been done.
• arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

---

🖥️ Tested on (X in brackets)

• Proxmox VE – Created on a Proxmox VE host and the app works.
• Incus – Created on an Incus host and the app works.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

---

🔍 Code & Security Review (X in brackets)

• Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials
• No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
• No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

---

📋 Additional Information (optional)

No git pull is used; updates go through apt because XWiki ships official Debian packages (see Description). The XWiki APT repo is a flat repository, so its official .list file is used instead of setup_deb822_repo. Happy to change this if a helper fits better.

Release tarballs: XWiki publishes versioned official releases (currently 18.9.0) with download archives (WAR, Jetty distribution) on xwiki.org and tagged source tarballs on GitHub. The script intentionally uses the official signed Debian packages from maven.xwiki.org instead, as recommended by the XWiki installation guide.

---

📦 Application Requirements (for new scripts)

• The application is at least 6 months old
• The application is actively maintained
• The application has 1,000+ GitHub stars
• Official release tarballs are published
• I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG

🌐 Source

• Website: https://www.xwiki.org
• Repository: https://github.com/xwiki/xwiki-platform
• Debian install guide: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/InstallationViaAPT
• Script request: [Script request]: XWiki ProxmoxVE#12671

---

🤖 AI Assistance (X in brackets)

• No AI used – Scripts were written without AI assistance.
• AI was used – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

Please describe to which degree, if any, an LLM was used in creating this pull request.

Claude (Anthropic) via the Claude app: Claude Sonnet 5.5 drafted the three files from my standalone XWiki installer, following AGENTS.md; Claude Opus 5.5 fixed the package filter in update_script after my test. Reasoning level: default. I tested everything on my Proxmox VE 9.2.26 host and fixed the issues found during testing.

[github-actions]

✅ Requirements check passed. Thanks for fixing the description — the stale mark has been removed.

[github-actions]

Try this script

ct/xwiki.sh, run in the Proxmox VE shell or on an Incus host:

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/freakms/DevScripts/add-xwiki \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/freakms/DevScripts/add-xwiki/ct/xwiki.sh)"

COMMUNITY_SCRIPTS_URL is not optional for ct/. Fetching the ct/ script from a
branch does not tell the engine where that branch is — with bash -c "$(curl …)"
there is no file on disk for the scripts root to be derived from, so it would fall
back to upstream main and look for the install script there.

Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Useful flags while testing

dev_mode=net logs every fetch with status and duration, so you can confirm the
branch is really being used. dev_mode=keep stops a failed build from deleting
the container along with the evidence.