Feature Request: Private Hosting Option about openupm HOT 5 CLOSED

Hi @sdcinglis,

OpenUPM isn't designed to be a self-hosting solution or to act as a private Git-to-registry bridge. I made some decisions to leverage public services to make it functional.

I'm unsure why GitHub Package Registry lacks list/search support. As long as it supports either the old /-/all search endpoint or the new /v1/search endpoint, the Unity editor should list your packages after setting up the related scopes. To verify, try npm --registry https://github-registry-hostname --verbose search your-keyword on your GitHub registry.

Publishing to a private registry can be straightforward if you automate the process with semantic-release-action. Check out the @semantic-release/npm docs for instructions on configuring a custom registry (publishConfig/NPM_CONFIG_REGISTRY and NPM_TOKEN).

If maintaining a self-hosted verdaccio is challenging, any other private registry, such as Azure Artifacts or npmjs, should work. I haven't tried any of them, so I don't have a preference.

from openupm.

Understood, but yeah GitHub Package Registry doesn't support either of the search APIs which is a very strange decision on their part IMO.

from openupm.

Hi. I have read somewhere that Azure Artifacts cannot be used directly as it doesn't support some required spec (https://developercommunity.visualstudio.com/t/Azure-Feed-NPM-Registry-not-aligned-with/1388626?space=21&entry=suggestion&q=NPM+Registry+API).
It seems it would need to be accessed behind something like this https://github.com/codebrewery/UPM-Proxy-GitHub.
So, having a direct private hosting would prob be an easier solution.
Thanks

from openupm.

The referenced article didn't mention if the Azure Artifacts support the old /-/all endpoint which can also be used for UPM search.

Anyway, creating a private verdaccio seems the most viable solution for now.

from openupm.

Closed the issue, because the service is not designed as an application for private usage.

from openupm.