[aroldobossoni]

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.

✍️ Description

Re-adds LiteLLM as a bare-metal Community Script for ProxmoxVED.

• ct/litellm.sh — LXC creation and update_script() using check_for_gh_release + fetch_and_deploy_gh_release
• install/litellm-install.sh — PostgreSQL 16, Python 3.12 via setup_uv, official release tarball, Prisma schema sync, systemd service
• json/litellm.json — metadata for the website

Tested on Proxmox VE 9.2.4 (Debian 13 LXC): install completes, prisma generate succeeds with venv on PATH, http://<CT_IP>:4000/health/liveliness returns healthy.

🔗 Related PR / Issue

Link: #14294 (previous removal from ProxmoxVE)

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

---

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

---

📋 Additional Information (optional)

Prior Docker-based submissions were rejected per AGENTS.md. This submission uses bare-metal installation only.

---

📦 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

• https://github.com/BerriAI/litellm
• https://docs.litellm.ai/

Made with Cursor

[tremor021]

This looks good to me already

[github-actions]

@aroldobossoni Recent activity detected. Removing stale label.

[michelroegl-brunner]

One thing, and this is not related to the script here is, why did you lie in the PR Template regarding the use of AI? We are most certainly not against the use of AI, some of us use it ourself. But to tick the "I did not Use AI box" and then have cursor as a co author is just a blatant lie, wich I can not unterstand. Can you elaborate here @aroldobossoni what made you do that?!?

[ComictypX]

Tested this PR on Proxmox VE 9.2.9 with the default Debian 13 LXC.

The container creation and LiteLLM installation itself completed successfully, but the installation failed during the Prisma/initialization step with LiteLLM 1.96.0:

ImportError: cannot import name 'get_flat_dependant'
from 'fastapi.dependencies.utils'

This then causes the misleading follow-up error:

ModuleNotFoundError: No module named 'proxy_server'

uv installed FastAPI 0.141.1. I first tried <0.141, which resolved to 0.140.13, but that version already lacks get_flat_dependant as well.

Pinning FastAPI to 0.140.6 fixes the LiteLLM import:

uv pip install --python .venv/bin/python 'fastapi==0.140.6'

After that:

.venv/bin/litellm --version

works correctly and reports LiteLLM 1.96.0.

I also had to ensure the proxy extras/Prisma dependencies were installed and use the schema provided by litellm_proxy_extras before running the Prisma migration. After that LiteLLM starts successfully and the web UI is reachable.

So it may be worth:

• pinning a compatible FastAPI version until the upstream LiteLLM issue is resolved;
• checking whether .[proxy,extra_proxy] should be installed instead of only .[proxy];
• using the Prisma schema shipped with litellm_proxy_extras for prisma generate / prisma migrate deploy.

[github-actions]

@aroldobossoni Closing stale PR due to inactivity (no commits for 7 days after stale label).