Download Images Section Needs Context

[luandro]

Type: Enhancement
Priority: P2
Labels: enhancement, documentation, ux

Description

The "Download images" section (accessed via hamburger menu) directly offers ISO files without context.

Issues

• Many users won't know what ISO files are for
• No maintenance strategy for keeping versions current

Suggested Improvements

• Add page explaining what these images are and how to use them
• Consider linking directly to source repositories for latest versions
• Provide installation guides

Reported by: Team review

[luandro]

We need a strategy to build these images automatically. Here's a proposal:

Automated Build Strategy

Option 1: GitHub Actions with Custom Runners

• Use self-hosted runners on dedicated hardware to build ARM64 images
• x86_64 images can be built on standard GitHub runners
• Trigger builds on schedule (weekly/monthly) or via manual dispatch

Option 2: Packer by HashiCorp

• Use Packer to define builds as code for both ISO and img formats
• Support multiple builders: cloud VMs for x86, physical machines for ARM64
• Version control the build templates in the repo

Option 3: Hybrid Approach (Recommended)

• Use GitHub Actions for CI/CD orchestration
• Custom build scripts that:
  • Pull latest base images (Debian/Ubuntu)
  • Apply customizations (YunoHost, CasaOS, CapRover)
  • Package into ISO/img formats
  • Upload to GitHub Releases

Implementation Steps

1. Create scripts/build-images/ directory with build scripts
2. Set up self-hosted runners for ARM64 builds
3. Create GitHub Actions workflow for automated builds
4. Configure release automation to publish artifacts

Would love feedback on which approach fits best with our infrastructure!