Description
First of all, thank you for this amazing project! As OpenCloud is geared toward professional, sovereign, and enterprise-grade environments, the current distribution channel for the Windows Desktop client creates significant friction for automated infrastructure deployment.
Currently, the Windows client is exclusively distributed through the Microsoft Store, while the NSIS executable installer built by the CI/CD pipeline remains hidden inside the temporary GitHub Actions workflow artifacts.
The Problem
Automated workplace management tools like SCCM / MECM or Microsoft Intune (Line-of-Business apps) require direct access to static raw binaries (.exe, .msix, or .msixbundle) in the GitHub Releases assets to stage, test, and push software packages to thousands of corporate workstations silently.
Proposed Solution
Since the CI/CD pipeline already successfully builds the NSIS executable, and the packaging layout for the Store is operational, we kindly request updating the release workflow to:
- Expose the existing NSIS
.exe installer directly into the GitHub Releases Assets, alongside the Linux AppImage and macOS packages.
- Enable the standalone
msix / msixbundle targets in the build configuration to generate and attach them to the release assets as well.
Benefits
- Enterprise Deployment Compatibility: Enables clean, native staging and provisioning via SCCM, Intune LOB, or custom internal deployment scripts (using standard silent switches like
/S or native commands like Add-AppxProvisionedPackage).
- Infrastructure Independence: Aligns with OpenCloud's philosophy of offering sovereign software independent of third-party cloud delivery networks when running in air-gapped or heavily isolated corporate environments.
- Predictable Lifecycles: Allows IT operations teams to lock and validate specific desktop client versions in production before rolling them out globally.
Thank you for considering this enhancement!
Description
First of all, thank you for this amazing project! As OpenCloud is geared toward professional, sovereign, and enterprise-grade environments, the current distribution channel for the Windows Desktop client creates significant friction for automated infrastructure deployment.
Currently, the Windows client is exclusively distributed through the Microsoft Store, while the NSIS executable installer built by the CI/CD pipeline remains hidden inside the temporary GitHub Actions workflow artifacts.
The Problem
Automated workplace management tools like SCCM / MECM or Microsoft Intune (Line-of-Business apps) require direct access to static raw binaries (
.exe,.msix, or.msixbundle) in the GitHub Releases assets to stage, test, and push software packages to thousands of corporate workstations silently.Proposed Solution
Since the CI/CD pipeline already successfully builds the NSIS executable, and the packaging layout for the Store is operational, we kindly request updating the release workflow to:
.exeinstaller directly into the GitHub Releases Assets, alongside the Linux AppImage and macOS packages.msix/msixbundletargets in the build configuration to generate and attach them to the release assets as well.Benefits
/Sor native commands likeAdd-AppxProvisionedPackage).Thank you for considering this enhancement!