Add AllStarLink Script

[DonLocke]

🛑 New scripts must first be submitted to ProxmoxVED for testing.
PRs for new scripts that skip this process will be closed.

---

✍️ Description

Added a new script to install AllStarLink with optional Allmon3.

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

---

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

📋 Additional Information (optional)

[michelroegl-brunner]

Please remove the header file.

[DonLocke]

Please remove the header file.

Why remove the header file?

[CrazyWolf13]

@DonLocke Because our Github-Action autogenerates it.

[github-actions]

⚠️ The script ct/allstarlink.sh failed with the following message:

curl: (22) The requested URL returned error: 404
TERM environment variable needs set.
TERM environment variable not set.

[DonLocke]

⚠️ The script ct/allstarlink.sh failed with the following message:
curl: (22) The requested URL returned error: 404 TERM environment variable needs set. TERM environment variable not set.

I don't understand what this means, can someone help me out and explain what this needs?

Edit: It looks like @MickLesk changed the url and it broke the action? Is the build script broken in this repo?

[MickLesk]

the action is currently broken, @michelroegl-brunner look at this the next days

[DonLocke]

Okay I have actually found a bug with the install, maybe a more advanced linux user can give me some guidance. This application depends on a kernal driver called dahdi, which seems to install fine but can't seem to be loaded by the application. Running modprobe dahdi is has a FATAL not found, and its looking in 6.8.12-9.pve but shouldn't it be looking in 6.1.0-32-amd64?

[MickLesk]

Proxmox LXCs use the kernel of the Main PVE, This is actually also the purpose of LXCs, i.e. like a shared kernel.

[DonLocke]

Proxmox LXCs use the kernel of the Main PVE, This is actually also the purpose of LXCs, i.e. like a shared kernel.

So then there isn't a way to do this? It has to be either privileged (So it can install the driver) or a VM? Or is there some workaround?

[MickLesk]

VM should be the better way

[DonLocke]

VM should be the better way

I'll try and refactor this script over the weekend then, thank you for the advice!

[DonLocke]

Can I get some eyes on this again? I think it should be all set, seems like the actions pass too.