[Question] BaGet as PowerShell module repository

❓ Question

Did anyone managed to run BaGet as PowerShell module repository sucessfully?

📑 Details

It seems like there are several discussions about the usage of BaGet and PowerShell in general.

Especially finding and installing packages via PowerShell (PackageManagement & PowerShellGet) seems to be unstable.

BaGet would be the first PackageRespository type using NuGet v3 API. Could the issues relate to this?

💣 Testing Details

• Server hosts http://baget:5555
  • latest BaGet docker image
• Client
  • Windows PowerShell 5.1 Desktop
    • PowerShellGet 2.0.4
    • PackageManagement 1.2.4
  • Ubuntu PowerShell 6.2.3 Core

🖼 Screenshots

🔖 Refs

• #199
• https://github.com/OneGet/oneget/issues/430

[TylerLeonhardt]

Hello everyone 👋 I work on the PowerShell team and wanted to say a couple things:

1. BaGet is amazing. A really sleek NuGet server AND client that works on .NET Core… I’m in love
2. PowerShellGet v2 is what ships in Windows as a part of Windows PowerShell so needless to say… PSGet v2 is here to stay for a long long time…
3. I was able to get Publish-Module working which is really exciting 😁
4. However, like others here, Find and Install do not work

It would be awesome to see the addition of the last couple of v2 APIs to get Find/Install working 🙂

[loic-sharma]

Hi, I apologize for the very long response. This requires supporting the legacy NuGet V2 APIs, which is tracked by https://github.com/loic-sharma/BaGet/issues/43. @Mizipzor and @jgagnaire made good progress on this (see https://github.com/loic-sharma/BaGet/pull/294 and https://github.com/loic-sharma/BaGet/pull/178).

I’ll admit that I’ve been dragging my feet here as I feel torn on adding “legacy” APIs to BaGet. However, I believe that supporting Powershell modules and fully replacing NuGet.Server’s feature set feels valuable enough. I will tackle this as part of BaGet V1 soon.