[Script request]: Huly

[e-ay]

Application Name

Huly

Website

https://huly.io/

Description

Huly is an all-in-one team workspace that combines project management, chat, documents, and real-time collaboration in one platform.

Due Diligence

• I have searched existing scripts and found no duplicates.
• I have searched existing discussions and found no duplicate requests.
• The application requested has 600+ stars on Github (if applicable), is older than 6 months, actively maintained and has release tarballs published.
• I understand that not all applications will be accepted due to various reasons and criteria by the community-scripts ORG.

[Dunky13]

I looked into whether I could contribute installation and update scripts for Huly. Based on the current documentation and contribution guidelines, I do not see a safe, maintainable route yet—but I may be missing an option.

Huly currently documents Docker Compose and Kubernetes for self-hosting. Its standard Compose deployment contains 14 services. The latest platform release provides source archives, but no ready-to-run native Linux artifacts for those services.

This appears to conflict with the Community Scripts guideline that new applications run bare-metal; Docker and Docker Compose installations are explicitly excluded.

Unless there is another supported deployment method, a native script would require creating our own layout for CockroachDB, Redpanda, Elasticsearch, MinIO, HulyKVS, and eight Huly application services. That would effectively make the script responsible for maintaining an unofficial Huly distribution.

Updates present a similar concern. Huly asks operators to review MIGRATION.md before every upgrade, since releases may require backups, configuration changes, new services, or data migrations. A generic download-and-restart updater would therefore not be safe.

My current assessment is that this request may need to remain open or deferred until Huly offers a supported native release with documented installation, service management, backup, and upgrade procedures.

@ArtyomSavchenko, is a supported non-container deployment available or planned? Any guidance from the Huly side would help determine whether a native script is feasible.

@MickLesk, I would appreciate your opinion on whether another supported approach—such as directing users to Huly’s Compose deployment inside a dedicated Docker VM—would be appropriate here. But given the comments I've seen in the past I assume the answer to be no, but want to double check.