Skip to content

[Feature] How should we handle binary files from Autobuild? #307

@ann0see

Description

@ann0see

Is your feature request related to a problem? Please describe.

Once the new build process is finished it will be possible to have direct download links to the binaries.
@nefarius2001 and me agreed that it would be great to include them in the website so that a new user doesn’t need to get in touch with another website (SourceForge). Problem: the link to the binaries will change once a new version is released and will have to be updated on the website.

Describe the solution you'd like

An easy way to change the download links can be achieved by saving them in the _config.yml file and then use a variable on all pages where these URLs should be included.

Describe alternatives you've considered

A permanent URL to the binary.

The current approach (automatically compile for "latest" and label the binaries *latest* & upload to a release called "latest" on GitHub has been dismissed since it involves too much complexity on the Autobild side.

Nefarius proposed some kind of redirect but this doesn’t seem to be possible cleanly with GH pages (GitHub always returns HTTP 200 and the current redirect implemented here is a hack).

Any thoughts here?

Additional context

jamulussoftware/jamulus#978

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions