You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case anyone hasn't heard by now @xoofx has resigned from Unity (source 1, source 2, source 3) and will no longer be maintaining this project and the feed he currently hosts in Azure with his MVP credits.
As of March 10 the feed will no longer be available so it will not be as easy as setting up the scopedRegistry in the manifest.jsonas stated in the instructions.
After that date everyone who wants to continue using the service without interruption will have to host it on their own.
This project publishes a Docker image in ghcr.io that can be consumed to create a container and host it as you wish. I list the most commonly used ones below:
Oh wow, what is so unexpected and unfortunate.
There is an alternative (NuGetForUnity)[https://github.com/GlitchEnzo/NuGetForUnity] project which doesn't allow to develop Unity packages with dependencies on NuGet packages like UnityNuGet does.
To be honest I have no idea how to manage that. Does anyone know a way to implement package dependencies in other way?
For example I am working on this package - Unity + EFCore + SQLite, which has dependencies on NuGet packages, it won't work without it.
In case anyone hasn't heard by now @xoofx has resigned from Unity (source 1, source 2, source 3) and will no longer be maintaining this project and the feed he currently hosts in Azure with his MVP credits.
As of March 10 the feed will no longer be available so it will not be as easy as setting up the
scopedRegistry
in themanifest.json
as stated in the instructions.After that date everyone who wants to continue using the service without interruption will have to host it on their own.
This project publishes a Docker image in ghcr.io that can be consumed to create a container and host it as you wish. I list the most commonly used ones below:
In this link you can see how to configure the Docker container and all the available parameters.
The text was updated successfully, but these errors were encountered: