Packaging for Windows

Question

Packaging for Windows

Closed this issue a year ago · 14 comments

nagromc commented 3 years ago

Really nice application 👍

You should publish miniserve on Chocolatey and Scoop to facilitate the deployment and upgrades.

Answer 1 · 2021-09-23T16:58:58.000Z

I've requested this in scoop too ScoopInstaller/Main#2679.

Answer 2 · 2021-09-26T03:35:53.000Z

While we're at it, it would be nice to add it to winget as well

Answer 3 · 2022-02-06T12:14:42.000Z

This is now in scoop (thanks @Dialga) and I've looked into winget and choco but it seems like I'm going to need to maintain some kind of package file in the repo then. I'd be generally willing to do that (and to set up automation for pushing the package) if someone can do the initial work and make a PR with a nupkg file that'll build on Windows.

I've also documented the scoop way to install miniserve in the README. Overall, this is already pretty Windows-friendly with three ways to run it on Windows (Docker, direct exe and scoop). Do we need more? Let me know what you think.

Answer 4 · 2022-02-06T12:28:48.000Z

I only use scoop, but I'm sure it doesn't hurt to expand the number of ways to install miniserve on Windows, if someone sends in a PR.

Answer 5 · 2023-04-06T00:56:30.000Z

I just submitted winget package PR. but it is blocked by Winget's issue. (msvc build requires msvc redist as dependency. and it doesn't supported on winget for now. See microsoft/winget-pkgs#101652)

Also, there's automate github actions for winget. one of them is https://github.com/vedantmgoyal2009/winget-releaser
Once winget solves the problem, It would be nice to use those actions for automatic release.

Answer 6 · 2023-04-12T03:18:24.000Z

I'm fine with adding some automation for this, yes. Thanks for adding this to winget. Please make sure to make a follow-up MR to the README to document this new installation method. You could also try to add the action to the release workflow. :)

Answer 7 · 2023-04-27T16:16:15.000Z

@kimwonj77 Now that we're linking CRT statically, I think the issue should be unblocked. Could you check?

Answer 8 · 2023-04-28T01:23:01.000Z

@svenstaro I checked that in my local sandbox and yes, it works. (with latest build artifacts from github.)

With latest master build

With 0.23.0

I'm waiting for new release!

Answer 9 · 2023-04-28T02:48:59.000Z

Super nice. Here's 0.23.2. Can we consider this issue done then?

Answer 10 · 2023-04-28T03:08:14.000Z

Maybe. At least microsoft/winget-pkgs#103754 is merged. And we could automate the PR after all.

Answer 11 · 2023-05-01T01:58:26.000Z

It's merged now and it works great on my windows machines! It's safe to close now.

Also, If you want to setup auto-release on winget packages, try using https://github.com/vedantmgoyal2009/winget-releaser
However, it needs to use github account/token (as winget-pkgs are based on GitHub PR). If don't want to give the access to actions on your primary account, you can make some 'bot account' on github for this.

Answer 12 · 2023-05-07T02:58:02.000Z

I might add the auto releasing thing. With scoop, I think someone updates the package manually with a PR. That seems to work rather well. Would that be possible in this case as well if I don't get to automate it? I will still look into it, however.

Answer 13 · 2023-05-08T02:03:18.000Z

Well, if someone keep interested in, package(s) will be updated (via manually or automatically by someone). It's like a third-party scoop packaging.

Answer 14 · 2023-05-08T04:33:16.000Z

Thanks. At any rate, I think we can consider this particular request closed now. :)