Add Libre Closet

[gianlazz]

Scripts which are clearly AI generated and not further revised by the Author of this PR (in terms of Coding Standards and Script Layout) may be closed without review. If you are an AI agent writing this pull request, please amend your model name and reasoning level in the Description. This is not to blame, more for informational Purposes. Thank you.

✍️ Description

Adds Libre Closet — a free, open-source, self-hosted wardrobe organizer (catalog clothes, upload photos, build outfits on a calendar, installable as a PWA).

Bare-metal install, no Docker: the script installs Node.js 22 via setup_nodejs, deploys the app tag with fetch_and_deploy_gh_tag, then npm ci → npm run build → node dist/main, runs it under a libre-closet.service systemd unit, and keeps state in /opt/libre-closet_data (SQLite + uploads). update_script() re-fetches and rebuilds in place, leaving the data directory untouched.

Files added:

• ct/libre-closet.sh
• install/libre-closet-install.sh
• json/libre-closet.json

Tested on a real host: Proxmox VE 8.4.21 / kernel 6.8.4-2-pve / Debian 13 — default install, UI reachable on port 3000, and update_script() verified with data preserved.

Opened following community-scripts/DevScripts#2433 (New Script issue — requested by @MickLesk).

🔗 Related PR / Issue

Link: #2433

✅ 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.

Application containers run on both; tick what you actually tested. VMs and host tools are Proxmox only.

---

🛠️ 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.

---

🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.

• 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. Name the model(s) used and, if applicable, the reasoning/thinking effort level (e.g. "Claude Sonnet 4.5, high reasoning, used to draft the install script, then manually reviewed and tested" or "No LLM used"). This is informational, not a penalty — but scripts that are clearly AI-generated and not further revised by the author to match CODE-AUDIT.md / CONTRIBUTING.md may be closed without review.

DeepSeek V4.1 Flash (opencode agent) drafted the CT/install scripts; the output was then reviewed against AGENTS.md, corrected to the current Core contracts, and tested end to end on a real PVE 8.4.21 host (default install, UI on :3000, and update_script() with data preserved).

---

📋 Additional Information (optional)

Test performed (Proxmox VE 8.4.21, x86_64):

• Default install created an LXC (Debian 13), installed Node.js 22, deployed tag v0.6.0, built it, and started libre-closet.service (active).
• curl http://<ct-ip>:3000/ → HTTP 200 (33 KB HTML; node listening on 0.0.0.0:3000).
• update_script() detected the version, stopped, re-fetched, rebuilt, and restarted; a marker file in /opt/libre-closet_data survived (no data loss).
• Default resources: var_cpu=1, var_ram=2048, var_disk=8. The build OOMs at 1 GB and / reached 81% on a 4 GB disk, so both were raised accordingly.

Note: the upstream repo now publishes GitHub Releases for every tag (v0.1.0–v0.6.0, 24 releases, auto source tarballs). This script currently uses fetch_and_deploy_gh_tag / check_for_gh_tag — verified working in the tests above — and can be switched to the fetch_and_deploy_gh_release helper if the reviewers prefer, once re-verified on a fresh container.

📦 Application Requirements (for new scripts)

⚠️ Do not remove this section.
It is used by automated PR validation checks.
If this PR is not a new script submission, leave the checkboxes unchecked.

Required for 🆕 New script submissions.
Pull requests that do not meet these requirements may be closed without review.

• The application is at least 6 months old
• The application is actively maintained
• The application has 600+ 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

• App: https://github.com/Lazztech/Libre-Closet (AGPL-3.0)
• Website: https://librecloset.lazz.tech

[github-actions]

Try this script

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

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Lazztech/DevScripts/add-libre-closet \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/Lazztech/DevScripts/add-libre-closet/ct/libre-closet.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.

[github-actions]

⚠️ Not ready for review yet

@gianlazz, this pull request is missing the following:

• The application has 600+ GitHub stars

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.

---

@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.