Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tomasz Sętkowski
    @tomzo
    First release is out. If you have any questions, issues, please ask here.
    Rolf Wessels
    @rolfwessels
    Hi
    I take it search has not been implemented yet ?
    I get the following error when I open the nuget browser. System.NotSupportedException: Not supported endpoint path /api/v2/Search() or action Search
    Rolf Wessels
    @rolfwessels
    Hmm, I seem to be able to push to it but never import anything into my solution.
    This is the 3rd linux nuget server that i have tried :-/
    Tomasz Sętkowski
    @tomzo
    @rolfwessels search is not implemented, I don't plan on implementing it. But we use this as private feed already for a couple of weeks now. push works, restore, install etc. Although we don't use visual studio. Only dotnet CLI and paket.
    Rolf Wessels
    @rolfwessels
    Ok, fair enough
    but in visual studio even the install-package does a search
    so I can't use it for now
    thanks anyway
    RomainWilbert
    @RomainWilbert
    Hi ! Does liget supports symbols ? Is it possible to push .symbols.nupkg files to the repository ?
    i get 409 erros when pushing symbols package files
    Tomasz Sętkowski
    @tomzo
    @RomainWilbert no, that's not implemented.
    RomainWilbert
    @RomainWilbert
    too bad
    thanks for answering
    Simon Oualid
    @soualid

    Hi ! Does liget supports symbols ? Is it possible to push .symbols.nupkg files to the repository ?

    went here to ask the same question, thanks! :-)

    Kieron Lanning
    @kieronlanning
    Hi! Is there a way to a) store the packages in Azure Blob Storage, and b) create and use read-only api-keys?
    Tomasz Sętkowski
    @tomzo
    Hi, a) azure support is dropped, you can look at baget for that. b) api keys are only for pushing, read-only access does not require auth
    Kieron Lanning
    @kieronlanning
    Thanks @tomzo. I was hoping for the read-only keys because it need to give a key per-client for a subscription model. So they may pay for a year for example, and after that either lock them out, or lock them to a maximum version.
    It's a shame about blob storage, it solves the problem of keeping data off the Kubernetes cluster and in a managed environment (where the provider will manage outages etc).
    Tomasz Sętkowski
    @tomzo
    @kieronlanning that's quite a requirement. The support was dropped because we don't use or test it. The main point of liget is to have minimal working server of good quality. Feel free to contribute, just be sure to include proper test coverage.
    thoscut
    @thoscut
    Currently the max package size is quite limited. Could it be increased to about 20GB?
    Tomasz Sętkowski
    @tomzo
    @thoscut the upload size is not limited in kestrel settings. Can you open and issue and post more details? your logs and error you are getting.
    thoscut
    @thoscut
    @tomzo it' the same issue described here loic-sharma/BaGet#191 for BaGet
    thoscut
    @thoscut
    The error message is exactly the same, you should be able to reproduce using a package file > 130MB (134217728 bytes)
    I could also see if I can provide you with a larger nupkg file for testing
    Tomasz Sętkowski
    @tomzo
    Thanks for the details. In Liget we try to reproduce all errors as part of automated testing, so the nupkg will have to be created during tests. It doesn't seem hard to fix though.
    thoscut
    @thoscut
    Ah, great. I used chocolatey to create the package for software distribution. I guess you can build a simple package around e.g. an iso image.
    The other thing I noticed was that in the v2 api the metadata request chocolatey sends isn't handled (results 404) instead of what looks like a field list (see https://chocolatey.org/api/v2/$metadata)