apidash icon indicating copy to clipboard operation
apidash copied to clipboard

Add WinGet install support

Open ashitaprasad opened this issue 11 months ago • 4 comments

API Dash is currently not available on WinGet. Contributors can help us in the following ways:

  1. Provide Step by step details on how to create a build and release it.
  2. CI/CD pipeline which prepares and publishes the build on WinGet whenever pubspec.yaml version is bumped.

Developers are requested to add (1) in https://github.com/foss42/apidash/blob/main/doc/dev_guide/packaging.md

Once (1) is completed (2) can be taken up.

Related issues & discussions - https://github.com/foss42/apidash/discussions/240

ashitaprasad avatar Jan 25 '25 01:01 ashitaprasad

My Step-by-Step Plan:

  1. Familiarize Myself with WinGet and FlatHub:

  2. Prepare the Build for WinGet:

  3. Submit to WinGet:

    • I will test the installer to ensure it works correctly on Windows.
    • I will follow the steps to submit the manifest and installer to the WinGet repository by creating a pull request in the WinGet-Pkgs GitHub repository.
  4. Set Up CI/CD for FlatHub:

    • I will learn the basics of CI/CD (Continuous Integration/Continuous Deployment) to automate the build and release process.
    • I will set up a CI/CD pipeline that prepares and publishes the build on FlatHub whenever the pubspec.yaml version is bumped. This might involve using tools like GitHub Actions or GitLab CI.
  5. Automate the Release Process:

    • I will configure the CI/CD pipeline to automatically detect changes in the pubspec.yaml version.
    • I will ensure the pipeline builds the Flatpak package and submits it to FlatHub.
  6. Testing and Verification:

    • I will test the entire process to ensure that the builds are correctly prepared and published on both WinGet and FlatHub.
    • I will verify that the application installs and runs correctly from both package managers.

By following these steps, I will be able to make API Dash available on WinGet and automate its release on FlatHub, ensuring a smooth and efficient distribution process.

abhinavs1920 avatar Jan 28 '25 15:01 abhinavs1920

@abhinavs1920 Why are you mixing WinGet with FlatHub .. these are two different issues.

ashitaprasad avatar Jan 28 '25 15:01 ashitaprasad

@abhinavs1920 Why are you mixing WinGet with FlatHub .. these are two different issues.

@ashitaprasad Second point of the issue says Flathub, it should be winget.

AnimeshAgarwal28 avatar Feb 13 '25 13:02 AnimeshAgarwal28

@abhinavs1920 Why are you mixing WinGet with FlatHub .. these are two different issues.

@ashitaprasad Second point of the issue says Flathub, it should be winget.

Thanks for pointing out @AnimeshAgarwal28

ashitaprasad avatar Feb 15 '25 12:02 ashitaprasad